SBL-GEN-00231 Process exited with error

Applies to:

Siebel CRM - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
z*OBSOLETE: IBM AIX5L Based Systems (32-bit)
***Checked for relevance on 28-FEB-2011***

Symptoms

Started JMS Receiver Component remains with the "running" state, but does not connect to JMS Server and does not start to pick up messages from the Queue.

1. Detailed  task log indicates no errors, but also does not show JMS works.

2. Siebel Server log file gets the "BL-GEN-00231 Process 2453540 exited with error" message for the JMS Receiver Component. The component self remains available.

Changes

Following setting were applied in Siebel Enterprise following information, given in the Siebel Bookshelf document: Transports and Interfaces: Siebel Enterprise Application Integration (EAI Volume 2): Java Business Service > Prerequisites for Implementing a Java Business Service.
1. The DLL parameter of the “JAVA” named subsystem (used by the JMS Receiver
Component) has been set to load the “libjvm.a” static library from the “classic” Java Virtual Machine of the IBM JDK Java 1.5 (jdk150_20070725):


2. The LIBPATH environment variable in the Siebel Server startup script was set to include following JDK folders:
/…/java/jdk/aix/ jdk150_20070725/jre/bin:
/…/java/jdk/aix/ jdk150_20070725/jre/bin/classic:
/…/java/jdk/aix/ jdk150_20070725/jre/lib
/…/java/jdk/aix/ jdk150_20070725/lib

/…/java/jdk/aix/ jdk150_20070725/jre/bin/classic/libjvm.a

3. The /…/java/jdk/aix/ jdk150_20070725/jre/bin/classic/libjvm.so file did not exist

Cause

Use of static JVM dll library: classic/../libjvm.a, while the dynamic one was required j9vm/.../libjvm.so

"Truss" traces, indicated that a dynamic JVM library: "libjvm.so" was not found in the "classic" JVM folder. It was present in the  "j9vm" JVM directory.

Solution

Following settings change was performed in Siebel Enterprise following information, given in the Siebel Bookshelf document: 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.

1. The DLL parameter of the “JAVA” named subsystem (used by the JMS Receiver
Component) has been changed to load the “libjvm.so” dynamic library from of “j9vm” Java Virtual Machine of the IBM JDK Java 1.5 (jdk150_20070725):

/…/java/jdk/aix/ jdk150_20070725/jre/bin/j9vm/libjvm.so

2. The LIBPATH environment variable in the Siebel Server startup script was amended to include only followig JDK folders:
/…/java/jdk/aix/ jdk150_20070725/jre/bin:
/…/java/jdk/aix/ jdk150_20070725/jre/bin/j9vm:
/…/java/jdk/aix/ jdk150_20070725/lib
The Change Request BUG 10559560 has been logged to ask for accordant documentation update in the EAI Book.
It has been fixed in Bookshelf 8.1

References

BUG:10559560 - [CR#12-1RRC6R1][FR#12-1RRC6RN] JMS RECEIVER DOES NOT READ FROM JMS QUEUE

Applies to:

Siebel Financial Services CRM - Version: 8.1 SIA [21039] to 8.1 SIA [21039] - Release: V8 to V8
IBM AIX on POWER Systems (32-bit)

Description

An error occurs while running of 'EAI JMS Transport' or 'Java Business Service' on Siebel version 8.1.1.x on AIX platform.

Likelihood of Occurrence

This affects EAI JMS Transport and Java Business Service running on AIX platform, when using :-

Sun JDK (instead of IBM Java SDK), or
IBM Java SDK but incorrect Java library being referenced in the Java (JVMSubsys) profile, or
LIBPATH and LD_LIBRARY_PATH does not reference the expected shared libraries.

Possible Symptoms

The following error will be encountered.

Error:

JVM Exception:java.lang.UnsatisfiedLinkError: net (No such file or directory)
JVM Exception:java.lang.NoClassDefFoundError: java.net.InetAddress (initialization failure)

Workaround or Resolution

1. Update the DLL parameter of the 'JVMSubsys' profile to reference the '/usr/java6/jre/lib/ppc/j9vm/libjvm.so' as per documentation on IBM JRE 1.6 on the IBM website for JNI calls from C/C++ code :-

http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.aix32.60/user/migrating_60.html

2. Update the environment variables LIBPATH and LD_LIBRARY_PATH  to include the directories containing the :

• JMS provider specific jar files and
• jre/lib/ppc and /jre/lib/ppc/j9vm (from IBM Java SDK install directory).

For example :
/u01/siebel/weblogic:/usr/java6/jre/lib/ppc:/usr/java6/jre/lib/ppc/j9vm

where : /u01/siebel/weblogic - is the directory containing JMS Provider specific (e.g Weblogic) jar files

NOTE :- When you build a C or C++ program that uses the invocation API, your LIBPATH must include the directories containing the JVM's shared libraries, /usr/java6/jre/lib/ppc/ and /usr/java6/jre/lib/ppc/j9vm, as well as the directories that contain the application's shared libraries.

Documentation Enhancement Request <Bug:13646352> has been filed, to request correction of the LIBPATH expression example for AIX, to have its JRE-related essential part look as:

...:/usr/java6/jre/lib/ppc:/usr/java6/jre/lib/ppc/j9vm:....

References

NOTE:1285062.1 - JRE version 1.6 required for all Siebel versions from Fix Pack 8.1.1.4 onward
SBL-EAI-05000
SBL-EAI-05102
NOTE:762463.1 - JMS receiver on AIX SBL-GEN-00231 Process exited with error
BUG:10559560 - [CR#12-1RRC6R1][FR#12-1RRC6RN] JMS RECEIVER DOES NOT READ FROM JMS QUEUE
BUG:13646352 - JBS: CORRECT LIBPATH VALUE FOR AIX