Fixes are available
APAR status
Closed as program error.
Error description
The queue manager ends unexpectedly. Symptoms vary but FDCs are typically observed from customer applications with Probe Id ZC007063 and ZC003010. There may also be FDCs produced from the execution controller with Probe Id ZC046010. This error only occurs in an environment whereby a multi-threaded server application is connecting to more than one queue manager.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Any users of WebSphere MQ using a multi-threaded server application to simultaneously connect to many different queue managers. Platforms affected: Windows **************************************************************** PROBLEM SUMMARY: The problem was caused by the fact that WebSphere MQ was not cleaning up the process cache of event handles when an application thread that is connected to a queue manager terminates without having issued an MQDISC request. As a result, another application thread requesting a new connection to a different queue manager could potentially end up using a cached event handle associated with the previous queue manager due to the checks in the process cache not being sufficiently unique to differentiate between two separate queue managers. This event handle was then posted when trying to establish communications with the new queue manager by putting messages on the IPCC pipe for that queue manager. This would end up posting the wrong queue manager.
Problem conclusion
WebSphere MQ was modified to ensure that the process cache of event handles is invalidated when a thread ends even if it does not perform an MQDISC against an MQ connection. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v6.0 Platform Fix Pack 6.0.2.9 -------- -------------------- Windows U200313 v7.0 Platform Fix Pack 7.0.1.1 -------- -------------------- Windows U200310 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
IC62566
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-14
Closed date
2009-10-07
Last modified date
2009-10-07
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
R700 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","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023