JVM Crashes On JNI_CreateJavaVM When Siebel Invokes EDQ Siebel Connector (Doc ID 2206206.1)

Last updated on NOVEMBER 21, 2016

Applies to:

Siebel CRM - Version 15.12 [IP2015] and later
Information in this document applies to any platform.

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION:      Siebel 15.0 + PatchSet 12 + EDQ Server 12.1.3.0.0.(794) + EDQ Siebel Connector 11.1.1.7.3.(996)(1)
SIEBEL APP O/S:       Oracle Solaris on SPARC (64-bit)

ISSUE STATEMENT:
----------------------------
Siebel application generates a crash when invoking JRE to send request to EDQ for data quality cleansing and matching.

ERROR MESSAGE:
--------------------------
Called from:
/global/u52/globpxtrui/siebel/siebsrvr/lib/libsslcosd.so:0x4dcdc
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/client/libjvm.so:0x4bd564
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/client/libjvm.so:JVM_handle_solaris_signal+0x940
/lib/libc.so.1:0xcb024
/lib/libc.so.1:0xbf6d4
/lib/libc.so.1:0xbf8bc
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/libjvm.so:JVM_NativePath+0x48 [ Signal 11 (SEGV)]
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/libzip.so:0xcc7c
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/libzip.so:0x173c
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/libzip.so:ZIP_Open+0x14
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/client/libjvm.so:0x274580
/usr/jdk/jdk1.6.0_22/jre/lib/sparc/client/libjvm.so:0x273dc0

STEPS TO REPRODUCE:
---------------------------------
The behaviour occurs as follows:

1. Install EDQ Siebel Connector

2. Edit the dnd.parms file to point to the location of the JRE libjvm.so file such as the following:

javalib:/usr/jdk/jdk1.6.0_22/jre/lib/sparc/client/libjvm.so
directory:/global/u52/globpxtrui/dnd/install
logfile:sdq%05d.log
jlogfile:jsdq%05d.log

3. Launch Siebel Client to create a new record, this triggers a call to EDQ through the EDQ Siebel Connector which uses the above /usr/jdk/jdk1.6.0_22/jre/lib/sparc/client/libjvm.so file. However, a crash is encountered at this point.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
--------------------------------------------
Due to the crash, the call to EDQ is not performed and this causes the Siebel Client application session to crash.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms