IBM Support

PM11735: USING THE WEBSPHERE MQ V7 64-BIT JMS PROVIDER NATIVE LIBRARIES IN WEBSPHERE APPLICATION SERVER FAILS

Fixes are available

6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • An attempt to use the Websphere MQ JMS provider in WebSphere
    Application Server (64 bit) for a bindings (jni native
    libraries) connection to WebSphere MQ v7 fails with
    a MQJMS2005 exception with the following linked exception:
    com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native
    JNI library 'mqjbnd' was not found. [3=mqjbnd]
    

Local fix

  • If the customer's system has no 32-bit JMS/Java applications
    trying to connect to the WMQ queue manager in the native
    bindings mode, then the file:
    /usr/mqm/java/lib/libmqjbnd.so
    can be renamed so that it is not available for the JVM to load
    resulting in only the 64 bit version being detected.
    Example, rename as follows:
     mv /usr/mqm/java/lib/libmqjbnd.so
        /usr/mqm/java/lib/libmqjbnd.so_NOT_IN_USE
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users IBM WebSphere Application Server, with*
    *                  64 bit application servers hosting          *
    *                  applications connecting to IBM WebSphere MQ *
    *                  Version 7.0 in Bindings mode                *
    ****************************************************************
    * PROBLEM DESCRIPTION: AMQ8568 error when attempting to        *
    *                      connect to WebSphere MQ Version 7.0     *
    *                      from a 64bit application server         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    On certain platforms, WebSphere Application Server attempts to
    load a "mqjbnd05" native library (from the WebSphere MQ server
    installation) in order to detect if the application server is
    32 or 64 bit, and configure the correct native library path
    for WebSphere MQ bindings connections accordingly.
    
    In WebSphere MQ Version 7.0, the native library name changed
    to "mqjbnd". The "mqjbnd05" library no longer exists.
    
    As the application server is not aware of this new library
    name, it incorrectly assumes the JVM is 32 bit and does not
    configure the native library path of the application server
    correctly.
    
    The incorrect native library path prevents WebSphere MQ from
    loading the 64 bit library, and the connections fail with
    AMQ8568 errors.
    
    The mechanism of detection of 64 bit application servers based
    on loading the "mqjbnd05" library is not used in all cases.
    As a result, the problem described in this APAR is most likely
    to occur when using WebSphere Application Server Version 6.0
    64 bit to connect to a WebSphere MQ Version 7.0 queue manager
    (with MQ_INSTALL_ROOT set).
    

Problem conclusion

  • The fix for this APAR updates WebSphere Application Server to
    look for the "mqjbnd" library as well as the "mqjbnd05"
    library. As a result the native library path is configured
    correctly when connecting to a WebSphere MQ Version 7.0 queue
    manager in bindings mode from a 64bit application server.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.0.2.43, 6.1.0.33, and 7.0.0.13.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM11735

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620400101

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-07

  • Closed date

    2010-05-24

  • Last modified date

    2010-05-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    PLAT MSG COM

  • Fixed component ID

    620400101

Applicable component levels

  • R100 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 6.0

Reference #: PM11735

Modified date: 24 May 2010