2 Replies Latest reply on Dec 5, 2012 12:55 PM by Juan Diego Ruiz-Oracle

    Unable to connect to MQ7.0 in BIND mode from Weblogic10.3.4 Cluster

      Unable to connect to MQ7.0 in BIND mode from Weblogic10.3.4 Cluster (Managed Servers)

      Issue in brief is we are able to connect to MQ7.0 from Weblogic10.0 admin server but not able to connect to MQ7.0 from Weblogic Cluster (Managed Servers).

      Below are the details:-

      1) Weblogic 10.3.4
      MQ Version:

      Admin Server :- adminserver
      Managed Server:- ms1
      Managed Server:- ms2
      Cluster:- cluster_1 (ms1,ms2)

      a) Admin Server (adminserver)
      When deployed the application on Admin Server (adminserver) its working fine, able to connect to MQ 7.0
      b) Cluster:- cluster_1 (ms1,ms2)
      When deployed the application on cluster_1(ms1,ms2) its failing with the error message:-

      ####<Jan 4, 2012 3:27:39 PM CET> <Warning> <EJB> <ahuoms30> <ms2> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <guest> <> <> <1325687259034> <BEA-010061> <The Message-Driven EJB: TestMDBean is unable to connect to the JMS destination: jms/queue/external/TestResponseQueue. The Error was:
      com.ibm.msg.client.jms.DetailedJMSException: JMSFMQ6312: An exception occurred in the Java(tm) MQI. The Java(tm) MQI has thrown an exception describing the problem. See the linked exception for further information.
      Nested exception: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd]
      Nested exception: java.lang.UnsatisfiedLinkError: no mqjbnd in java.library.path>

      Error Occurs because it is not able to find the mqjbnd in java.library.path.
      The JAVA_LIB_PATH="/opt/mqm/java/lib64" valus is set in the startup script for both the Admin Server (adminserver) and cluster_1 (ms1,ms2),
      working fine for Admin Server (adminserver) but not for cluster_1 (ms1,ms2).

      Connection towards MQ is not working for the clusters(ms1,ms2) when compared with the Admin Server (adminserver) as all the settings in scripts are same.

      Does anyone have experience similar issue and solved this issue, please let me know.