Fixes are available
APAR status
Closed as program error.
Error description
When using WebSphere MQ V7 classes for JMS with automatic client reconnection enabled, after a broken connection a NullPointerException is thrown during a reconnection attempt. The WebSphere MQ classes for JMS then produce an FDC showing: Probe ID :- JO719001 and the following stack trace: Stack Trace:1 :- java.lang.NullPointerException at com.ibm.mq.jmqi.remote.api.RemoteHconn.wakeDispatchThread(Remote Hconn.java:52 8) at com.ibm.mq.jmqi.remote.impl.RemoteReconnectThread.reconnect(Remo teReconnectThread.java:476) at com.ibm.mq.jmqi.remote.impl.RemoteReconnectThread.run(RemoteReco nnectThread.java:121) at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTas k(WorkQu eueItem.java:209) at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem. runItem(SimpleWorkQueueItem.java:100) at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(Wo rkQueueItem.java:224) at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.run WorkQueueItem (WorkQueueManager.java:298) at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManage rImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementat ion.java:1214)
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ V7 classes for JMS or WebSphere MQ V7 classes for Java where automatic client reconnect functionality has been enabled. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: If no asynchronous messaging occurred on the remote connection before the reconnection attempt, waking the dispatch thread that handles asynchronous message consumption resulted in a NullPointerException as this thread would not have been created.
Problem conclusion
The code has been altered to ensure the asynchronous message consume dispatch thread has been created prior to the broken connect, waking it only in the case it exists. This change prevents the NullPointerException from occurring. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.1 Platform Fix Pack 7.1.0.3 -------- -------------------- Windows 7.1.0.3 AIX 7.1.0.3 HP-UX (Itanium) 7.1.0.3 Solaris (SPARC) 7.1.0.3 Solaris (x86-64) 7.1.0.3 iSeries 7.1.0.3 Linux (x86) 7.1.0.3 Linux (x86-64) 7.1.0.3 Linux (zSeries) 7.1.0.3 Linux (Power) 7.1.0.3 zOS 7.1.0.3 Platform v7.5 -------- -------------------- Multiplatforms 7.5.0.1 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
IC87103
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
2012-10-09
Closed date
2012-11-01
Last modified date
2012-11-01
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