Environment:

Solaris 8, JVM1.3.1_03
WebLogic Server 70sp1 and MQSeries 5.3

Description:

One of BEA's biggest customers in France would like to integrate WebLogic
Server (running on top of Sun JVM) with MQSeries. This integration is done
using an MDB (Message Driven Bean) deployed on WebLogic Server. The MDB
listen to an MQSeries queue. The customer needs XA support so MQSeries is
configured in binding mode. This means that MQSeries (IBM) native libraries are
loaded in the JVM memory and accessed via JNI.

The server starts correctly and the MDB is able to retrieve messages from
the MQSeries queue but as soon as one accesses the WLS console (which is
merely a webApp deployed on the same VM as the MQSeries libs), the JVM
crashes. Please note that there is no native code involved on the WebLogic
side during this scenario. When the crash occurs the JVM does not produce a
core.

Various tests have been done:
- Tests with JVM1.3.1_03, 1.3.1_06 debug (provided by Sun Support), JVM1.4
all produce the same problem.
   Most of the dbx stack traces we got show that the crash seems to occur in
libjvm.so.
- Decouple the WebLogic console and the MQSeries libs by loading them in
different VMs.
   In this scenario, 2 WebLogic Servers were configured: one Admin on which
the console runs and another Managed on which the MDB and MQSeries integration are deployed. The problem still occurs: in one instance, the MDB was reading messages from the MQSeries queue when the related VM crashed, meaning that this is not specifically related to the console.

Impact:

The issue is logged as Severity 1 problem at BEA and customer needs
resolution or at least a precise diagnosis ASAP.

2. If MQseries are disabled Weblogic Server works fine

3. IBM didn't cooperate to solve this problem