A fix is available
APAR status
Closed as program error.
Error description
When an XMS .NET application is connecting to a WebSphere MQ mutli-instance queue manager Version 7.1 using administered objects, the automatic client reconnection fails. That is, XMS .NET never reconnects following a fail-over. This behavior is seen with administered objects stored in FileContext, LDAP server/JNDI.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All the XMS .NET application using Client Auto Reconnection feature with Administered objects. Platforms affected: Windows **************************************************************** PROBLEM SUMMARY: When the Client Auto Reconnection properties are set on the ConnectionFactory using the FileContext/JNDI service. During runtime, when XMS .NET client looks up for this object, it was failing to read the Reconnection related properties from the retrieved object property map. Due to this reason, XMS .NET failed to reconnect following a fail over.
Problem conclusion
XMS .NET code has been fixed to read the Reconnection related properties from the Administered objects and use them for reconnecting on a fail over. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.1 Platform Fix Pack 7.1.0.3 -------- -------------------- Windows 7.1.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
IV32457
Reported component name
MSG SRVCS CL .N
Reported component ID
5724M2100
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-26
Closed date
2013-01-25
Last modified date
2013-01-25
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
MSG SRVCS CL .N
Fixed component ID
5724M2100
Applicable component levels
R210 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCRTPP","label":"SupportPac"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
25 January 2013