A fix is available
APAR status
Closed as program error.
Error description
WebSphere MQ Classes for JMS V7.0.1: A NullPointerException is thrown when a client application that has automatic client reconnection enabled attempts to create a remote connection to a Z/OS Queue Manager. The following exception is thrown: java.lang.NullPointerException at com.ibm.mq.jmqi.internal.JmqiTools.getQueueManagerInfo (JmqiTools.java:568) at com.ibm.mq.jmqi.remote.internal.RemoteHconn.loadInfo (RemoteHconn.java:2661) at com.ibm.mq.jmqi.remote.internal.RemoteHconn.getQsgName (RemoteHconn.java:2578) at com.ibm.msg.client.wmq.internal.WMQConnection.<init> (WMQConnection.java:542) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7Pr oviderConnection(WMQConnectionFactory.java:7192) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProv iderConnection(WMQConnectionFactory.java:6583) at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConn ection(JmsConnectionFactoryImpl.java:295) at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection (MQConnectionFactory.java:6232) at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection (MQQueueConnectionFactory.java:115)
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ V7.0.1.9 Classes for JMS (or later) who have enabled automatic client reconnect and are attempting to establish a remote connection to a z/OS Queue Manager. This includes users of: - The WebSphere MQ V7.0.1 Classes for JMS. - The WebSphere MQ V7.0.1 Resource Adapter. - The WebSphere Application Server V7.0 and V8.0 WebSphere MQ messaging provider. - The WebSphere Application Server V6.1 WebSphere MQ messaging provider who have configured the WebSphere variable MQ_INSTALL_ROOT to point to a WebSphere MQ V7.0.1 installation. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: As part of the call to create a connection to the Queue Manager the WebSphere MQ classes for JMS query a number of properties/ values from the Queue Manager and store them away for further use later on in the connection process. When automatic client reconnection was enabled and the client attempted to retrieve the Queue Sharing Group Name (qsgName) the WebSphere MQ Classes for JMS attempted to query the queue manager using an invalid connection handle (HCONN). This resulted in the NullPointerException being thrown.
Problem conclusion
The WebSphere MQ Classes for JMS no longer use the invalid connection handle. The Queue Sharing Group Name is now retrieved using the correct connection handle (HCONN). --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.12 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
IV46727
Reported component name
WMQ AIX V7
Reported component ID
5724H7221
Reported release
710
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-07
Closed date
2013-09-13
Last modified date
2014-01-13
APAR is sysrouted FROM one or more of the following:
PM93940
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ AIX V7
Fixed component ID
5724H7221
Applicable component levels
R710 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":"710","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023