Fixes are available
APAR status
Closed as program error.
Error description
A JMS application attempts to make a bindings mode connection to a queue manager. The following exception is seen, and the application fails to connect to the queue manager: 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. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nat ative Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Nati veConstructorAccessorImpl.java:56) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( DelegatingConstructorAccessorImpl.java:39) at java.lang.reflect.Constructor.newInstance(Constructor.java :527) at com.ibm.msg.client.commonservices.j2se.NLSServices.createE xception(NLSServices.java:314) at com.ibm.msg.client.commonservices.nls.NLSServices.createEx ception(NLSServices.java:228) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.crea teV7ProviderConnection(WMQConnectionFactory.java:6759) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.crea teProviderConnection(WMQConnectionFactory.java:6151) at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.crea teConnection(JmsConnectionFactoryImpl.java:280) at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection( MQConnectionFactory.java:6143) at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConn ectionFactory.java:6172) at MyApp.MyMethod(MyApp.java:47) at MyApp.main(MyApp.java:31) Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. For a client installation this is expected. [3=mqjbnd] at com.ibm.mq.jmqi.local.LocalMQ$1.run(LocalMQ.java:307) at java.security.AccessController.doPrivileged(AccessControll er.java:228) at com.ibm.mq.jmqi.local.LocalMQ.initialise_inner(LocalMQ.jav a:268) at com.ibm.mq.jmqi.local.LocalMQ.initialise(LocalMQ.java:230) at com.ibm.mq.jmqi.local.LocalMQ.<init>(LocalMQ.java:1174) at com.ibm.mq.jmqi.local.LocalServer.<init>(LocalServer.java: 193) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nat tive Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Nati veConstructorAccessorImpl.java:56) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( DelegatingConstructorAccessorImpl.java:39) at java.lang.reflect.Constructor.newInstance(Constructor.java :527) at com.ibm.mq.jmqi.JmqiEnvironment.getInstance(JmqiEnvironmen t.java:717) at com.ibm.mq.jmqi.JmqiEnvironment.getMQI(JmqiEnvironment.jav a:651) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.crea teV7ProviderConnection(WMQConnectionFactory.java:6751) ... 6 more Caused by: java.lang.UnsatisfiedLinkError: mqjbnd (Not found in java.library.path) at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java :1018) at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoad er.java:982) at java.lang.System.loadLibrary(System.java:506) at com.ibm.mq.jmqi.local.LocalMQ.loadLib(LocalMQ.java:1141) at com.ibm.mq.jmqi.local.LocalMQ$1.run(LocalMQ.java:283) ... 18 more It is not immediately apparent what this exception means, or what needs to be configured to make the application work.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: The new diagnostic output data which is enhanced by the code change associated with this APAR affects users of the WebSphere MQ classes for Java and WebSphere MQ classes for JMS, who have applications which are attempting to establish a communication channel to a queue manager using 'bindings' mode. A 'bindings' mode connection is where the client application and queue manager communicate using the host system's memory, as opposed to the TCP/IP stack, which is referred to as a 'client' mode, or remote connection. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: APAR IZ84448: http://www.ibm.com/support/docview.wss?uid=swg1IZ84448 describes the two forms of communication methods by which the WebSphere MQ classes for Java/JMS can use. APAR IZ84448 also added additional diagnostic data to the trace, to assist IBM Support in resolving problems concerning the application's connection configuration. The standard error message which is thrown back to the application when a bindings mode connection attempt fails due to the loading of the native library is of the following form: AMQ8568: The native JNI library 'mqjbnd' was not found. For a client installation this is expected. [3=mqjbnd] While this may provide a WebSphere MQ experienced user with sufficient information to resolve the problem, it does not satisfactorily describe the problem such that the user can be expected to resolve the configuration issue on their own.
Problem conclusion
This APAR enhances the information which is presented within the Java Exception when the bindings library fails to load. This information is presented in the following form: Caused by: com.ibm.mq.jmqi.local.LocalMQ$3: CC=2;RC=2495; AMQ8598: ---------------------------------------------------------------- | Failed to load the WebSphere MQ native JNI library: 'mqjbnd'. | | The JVM attempted to load the platform native library | 'mqjbnd', which was mapped to the filename: 'libmqjbnd.so'. | | When attempting to load the library, the JVM reported the the | error message: | 'mqjbnd (Not found in java.library.path)' | | The JVM's bit-size is: '64' | | The library path which was used to locate this library was: | '*** Configured java.library.path **************************** | "/opt/ibm/ibm-java-x86_64-60/jre/lib/amd64/default" | "/opt/ibm/ibm-java-x86_64-60/jre/lib/amd64" | "/usr/lib" | *************************************************************' | | Check that the bit size of the JVM matches the bit size of | the first native library file located within this | java.library.path directory list. | | The native library 'mqjbnd' is used by the WebSphere MQ | classes for Java and WebSphere MQ classes for JMS when | creating a connection to the queue manager using a 'bindings' | mode connection. A bindings mode connection is a connection | which uses the system's memory to communicate with the queue | manager, as opposed to a 'client' mode connection which uses | a TCP/IP socket. | | In order to communicate with a queue manager using a bindings | mode connection, the queue manager must be located on the | same system as the WebSphere MQ classes for Java/JMS. If this | is not the case in your environment, consider reconfiguring | the application to utilise client mode connections. ---------------------------------------------------------------- The data provided describes: The JVM bit-size The value of the JVM's java.library.path at the point of loading the library. The name of the file which the attempt was made to load. This is sufficient information to permit the user to resolve the majority of mis-configured systems. --------------------------------------------------------------- The fix is targeted for delivery in the following: v7.0 Platform Fix Pack 7.0.1.11 -------- -------------------- Windows 7.0.1.11 AIX 7.0.1.11 HP-UX (PA-RISC) 7.0.1.11 HP-UX (Itanium) 7.0.1.11 Solaris (SPARC) 7.0.1.11 Solaris (x86-64) 7.0.1.11 iSeries 7.0.1.11 Linux (x86) 7.0.1.11 Linux (x86-64) 7.0.1.11 Linux (zSeries) 7.0.1.11 Linux (Power) 7.0.1.11 zOS 7.0.1.11 v7.1 Platform Fix Pack 7.1.0.4 -------- -------------------- Windows 7.1.0.4 AIX 7.1.0.4 HP-UX (Itanium) 7.1.0.4 Solaris (SPARC) 7.1.0.4 Solaris (x86-64) 7.1.0.4 iSeries 7.1.0.4 Linux (x86) 7.1.0.4 Linux (x86-64) 7.1.0.4 Linux (zSeries) 7.1.0.4 Linux (Power) 7.1.0.4 zOS 7.1.0.4 Version v7.5 -------- -------------------- Fix available in: 7.5.0.3 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IC89380
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-07
Closed date
2013-06-26
Last modified date
2013-08-14
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
WMQ WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R701 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023