SBL-EAI-05006: Failed to load the JVM Dll. Check that the specified dll name is correct.

Applies to: Siebel CRM - Version: 8.0.0.2 SIA [20412] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms
Customer encountered the following error when starting a task for JMSReceiver server component using Siebel server command line:

start task for comp JMSReceiver with ReceiverConnectionSubsystem=CRMAEAIJMSConnSubSys,ReceiverDataHandlingSubsystem=SiebelEcho,ReceiverMethodName=ReceiveDispatchSend
SBL-ADM-60070: Error reported on server 'ss_migsvil1' follows:
SBL-SVR-01014: Internal: Could not send the HELLO message: (null)
SBL-NET-01033: The SISNAPI handshake timed out. The Siebel Service may not be running.

Cause
Error was caused by the DLL parameter used/required by this component was referencing the wrong version of the DLL/.so library file.

Customer enabled detailed logging on the server component, reproduced the error, inspected the log file and was able to see to detailed error message indicating that "SBL-EAI-05006: Failed to load the JVM Dll"

Customer is on HP-UX, they were setting the DLL parameter to value:

"/opt/java1.5/jre/lib/IA64W/server/libjvm.so"

However, this is not the correct version to use. The correct version for HP-UX is from "/opt/java1.5/jre/lib/IA64N/server/libjvm.so"

The library file that should be used is from "/opt/java1.5/jre/lib/IA64N/server/libjvm.so", as this is the version documented in Siebel Bookshelf:

Siebel Bookshelf > Siebel Application Deployment Manager Guide > Configuring and Administering the ADM Framework > Process of Configuring the ADM Framework after Installing Siebel Management Server and Siebel Management Agent > Configuring the Siebel Server for ADM:

Select the JVM DLL Name parameter, and verify that the entry in the Value field references the location of the jvm.dll file in the JRE installation.

The JVM DLL Name parameter value depends on the operating system. See the following table for the values for the different operating systems.

Operating System Parameter Value

Windows: JRE_HOME/bin/client/jvm.dll
Solaris: JRE_HOME/lib/sparc/client/libjvm.so
AIX: JRE_HOME/bin/j9vm/libjvm.so (IBM JRE)
Novell SUSE Linux JRE_HOME/lib/i386/client/libjvm.so
Oracle Enterprise Linux JRE_HOME/lib/i386/client/libjvm
HP-UX JRE_HOME/lib/IA64N/server/libjvm.so

SolutionOnce the DLL parameter was updated to "/opt/java1.5/jre/lib/IA64N/server/libjvm.so", the error no longer occurred.

The following change request has been logged to include the above dll/.so library information into EAI Guide under JMS Transport section as well:

Documentation CR # 10545448 - include documentation of jvm.dll and libjvm.so versions in EAI Guide








































Applies to: Siebel System Software - Version: 7.7.2 SIA [18325] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1584186765.

SymptomsAfter configuring the environment as per bookshelf indications to invoke a java business service, when attempting to run one of its methods on the Business Simulator the following message is observed:

"Failed to load the JVM Dll. Check that the specified dll name is correct (SBL-EAI-05006)"

This problem occurs under Solaris. The code and configuration had been successfully tested under Windows.

Cause64 bit jvm was used.

Solution
The reason, the JVM DLL could not be loaded by the Siebel Object Manager call, is the difference in its CPU-bits platform/compilation:
- 32-bits architecture for Siebel Object Manager C++ run-time environment (including 'MainWin' run-time)
- 64-bits for currently used JVM shared library: <JDK_HOME>/jre/lib/sparcv9/server/libjvm.so

Suggestion: Modify the 'DLL' parameter in the used 'JAVA' named sub-system, to load/invoke a 32-bits JVM shared library, provided with the accordant JDK version.This can be either 32-bits client JVM library: <JDK_HOME>/jre/lib/sparc/client/libjvm.so
or 32-bits server JVM library: <JDK_HOME>/jre/lib/sparc/server/libjvm.so


Note: you should not modify any of 'siebmt*' Siebel Server Component startup scripts, since these changes are not necessary (and even not supported) for successful use of the EAI Java integration approach on the SUN Solaris platform

BUG: 10483157 has been logged to ask for accordant Siebel product documentation enhancement (to note what 64-bit JVM can not be used the for 32-bits implementation of an EAI Java Business Service).


ReferencesBUG:10483157 - NOTE, WHAT 64-BITS JVM CAN NOT BE USED THE FOR 32-BITS IMPLEMENTATION OF AN EAI JBS










































Applies to: Siebel Clinical Manager - Version: 7.8.2.4 SIA [19224] - Release: V7
Information in this document applies to any platform.

Symptoms
Environment:
-------------------

Product: Siebel Clinical Manager
Version: 7.8.2.4 SIA [19224]
OS platform: HP-UX PA-RISC (64-bit)
DB platform: Oracle Server - Enterprise Edition
Env: dev


Statement of Issue:
-----------------------------
With the parameter OM - Preload SRF Data set to FALSE, the JMSReceiver task fails with an error on start-up.


Error:
-------
ObjMgrBusServiceLog Error 1 0 2010-01-21 13:41:02 (javabsvc.cpp (164)) SBL-EAI-05006: Failed to load the JVM Dll. Check that the specified dll name is correct.

Business Impact:
-------------------------
JMSReceiver is required to pick messages up from a JMS queue and process them.

Cause
The environment variable SHLIB_PATH is not set correctly in <siebsrvr>/siebenv.sh.

The environment variable LD_PRELOAD is not set in the following files:

/bin/siebshw
/bin/siebprocw
/bin/siebsessw

SHLIB_PATH is set as follows in siebenv.sh:

SHLIB_PATH=${SHLIB_PATH}:${SQLANY}/lib
SHLIB_PATH=${SHLIB_PATH}:/opt/java1.4/jre/lib/PA_RISC2.0:/opt/java1.4/jre/lib/PA_RISC2.0/server:/opt/java1.4/jre/bin/PA_RISC2.0
export SHLIB_PATH

SHLIB_PATH should not include multiple java directories, which it does in this case.

LD_PRELOAD is set as follows in siebmtshw.sh:

export LD_PRELOAD=/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl

LD_PRELOAD is not specified in siebshw.sh, siebprocw.sh and siebsessw.sh.

Solution1. Set SHLIB_PATH as follows in siebenv.sh:

SHLIB_PATH=${SHLIB_PATH}:${SQLANY}/lib
SHLIB_PATH=${SHLIB_PATH}:/opt/java1.4/jre/lib/PA_RISC2.0;
export SHLIB_PATH

2. Add the following entries to /bin/siebshw, /bin/siebprocw and /bin/siebsessw:

LD_PRELOAD=/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl
export LD_PRELOAD

3. Restart the machine so that the changes take effect.

ReferencesNOTE:818975.1 - Automatically restarted JMSReceiver task fails with “Failed to load the JVM Dll.”.






































Applies to: Siebel Service - Version: 7.8.2.7 [19234] and later [Release: V7 and later ]
Information in this document applies to any platform.

SymptomsCustomer experienced the following error while trying to execute a Java Business Service (JBS) on a 64 bit HP UX B.11.11 U 9000/800 box, whereas the same JBS worked fine on a windows environment:

Error: SiebelError: Failed to load the JVM Dll. Check that the specified dll name is correct.(SBL-EAI-05006)

CauseFrom the detailed log file, it was observed that parameters provided for the JAVA named subsystem was not provided correctly (per recommendation in Bookshelf).

SolutionTo verify the behaviour, internal tests were conducted on standard siebel application on HP UX platform, in which an EAI JAVA Business Service was implemented to execute the sample java code provided as an example in Bookshelf > Transports and Interfaces: Siebel Enterprise Application Integration > Java Business Service > Example of a Java Business Service. It worked fine with the below set up using JRE 1.4

1) Creating JAVA named subsytem:

The JAVA subsystem was created with the following parameters:

DLL = /opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl
CLASSPATH = /vol1/sia78ora/sumana/Siebel.jar:/vol1/sia78ora/sumana/SiebelJI_enu.jar:/vol1/sia78ora/sumana:.
VMOPTIONS = -Xrs -Djava.compiler=NONE -Xusealtsigs

Since Siebel is a 32-bit application, it need to access 32 bit libraries. In HP UX B11.11 the directory PA_RISC2.0 contains the 32 bit libraries ( Refer to link: http://docs.hp.com/en/JDKJRE60RN/jdk_rnotes_6.0.01.html#HP-UX_requirements). So the DLL paramter needs to specify the complete path of the the java runtime library (i.e libjvm.s) contained in PA_RISC2.0 of the HP UX installation directory.

Also it is important to the use the additional switch “-Xusealtsigs” for the parameter VMOptions .

2) Platform specific settings for HP UX OS:

For HP UX platform, the below environment variables were set as below:

LD_PRELOAD=/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl
export LD_PRELOAD
SHLIB_PATH=${SHLIB_PATH}:/opt/java1.4/jre/lib/PA_RISC2.0;
export SHLIB_PATH

For more details on creating JAVA named subsytem and other platform specific settings, please refer to:

Bookshelf > Transports and Interfaces: Siebel Enterprise Application Integration > Java Business Service > Prerequisites for Implementing a JBS
































Applies to: Siebel System Software - Version: 7.8.2.6 SIA [19230] - Release: V7
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.6 [19230] ESN Cons Goods
Database: Oracle 10.2.0.2
Application Server OS: IBM AIX 5L 5.2 ML6
Database Server OS: IBM AIX 5L 5.3

This document was previously published as Siebel SR 38-3502083683.

SymptomsWe are in the testing phase of an outbound web service integration that requires the encryption of the message sent.
In order to encrypt the message, our client has developed a java jar file that we call from our workflow through the Java Business Service.
This is working perfectly in our local machine but we have come across several errors while running it in the siebel server:
1. Firstly, we received the following error: "SiebelError: Error al llamar a JNI_CreateJavaVM.(SBL-EAI-05003)" which we identified with Siebel Alert 1308 (Doc ID 475359.1). We changed the JVM version to 1.5.0.
2. Then we received the following error: "SiebelError: Error al cargar el Dll JVM. Compruebe que el nombre de archivo dll es correcto.(SBL-EAI-05006)". Looking into SR 38-1584186765 we found out we needed the JVM 32-bit installation. We changed it accordingly.
3. Now, the workflow process hangs in the "Obtener Firma" step when we call the Java Business Service, without receiving any detailed error message.

We have attached the following information:
1. WfProcMgr_8310.log: the log of the Workflow Process executed with event parameters to 4.
2. CK EAI Java Business Service Web Service.sif: the Java Business Service
3. CK Transformar Venta Asistida.sif: BS that calls to Java BS (with the "Obtener Firma" method).
4. CK Envio Online Venta Asistida.xml: the workflow process.

The environment variables are as follows:
LIBPATH
/softOracle/app/oracle/product/10.2.0/db_1/lib32:/softOracle/app/oracle/product/10.2.0/db_1/lib:/usr/lib:/usr/local/lib:/usr/java5/jre/lib:/usr/java5/jre/bin/classic:
LD_LIBRARY_PATH
/softOracle/app/oracle/product/10.2.0/db_1/lib:/coblib:/usr/java5/jre/lib:/usr/java5/jre/bin/classic:

The java subsystem definition is as follows:
Profile: JAVA
Alias: JAVA
Subsystem Type: JVMSubSys
Profile Parameters:
DLL: "/usr/java5/jre/bin/classic/libjvm.a"
CLASSPATH:"/crm_dv/siebel/siebsrvr/classes/Siebel.jar:/crm_dv/siebel/siebsrvr/classes/encrypt.jar:/crm_dv/siebel/siebsrv...

CauseError on the LIBPATH definition on AIX.

SolutionMessage 1Customer was trying to run a Java Business Sevice with Siebel Server on AIX and had followed the steps in bookshelf "Transports and Interfaces: Siebel Enterprise Application Integration > Java Business Service > Prerequisites for Implementing a JBS"

However, whe trying to call the JBS the OM would hang.
Also tried "EAI JMS Transport" , "CheckClassPath". this would either hang, crash or restart the OM.

This was tracked down to being a LIBPATH issue.

To be safe.. ensure the LIBPATH has following :

JAVADIR/jre/bin/classic
JAVADIR/jre/lib
JAVADIR/lib
JAVADIR/jre/bin << IMPORTANT AS it has "libjava.a"

Raised Change Request #12-1MB605R as we dont document all the correct directories for LIBPATH on AIX


keywords: crash, hang, jvm, aix, libjvm.so, libjvm.a,libjava.a

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software Keywords
CLASS; JAR; JRE; CLASSPATH; AIX
Errors
SBL-EAI-05006; SBL-EAI-05003