IBM Support

WebSphere MQ adapters do not reconnect when the WebSphere server is moved over to another MSCS cluster node

Troubleshooting


Problem

WebSphere MQ adapters do not reconnect when the WebSphere server is moved over to another MSCS cluster node

Symptom

2 node MSCS cluster runs WebSphere, and GIS connects to that cluster to communicate with WSMQ. Whenever one of the nodes in the MSCS cluster is taken down and WSMQ resources are failed over to the other node, GIS loses the ability to connect to WSMQ and all the WSMQ adapters get disabled.

The GIS Websphere MQ adapters are not reconnecting after the Websphere MQ MSCS cluster server goes down and comes back up. Websphere MQ in the customer~s environments is in a MSCS cluster and they are moving it back and forth between the 2 servers, then the GIS Websphere MQ adapters are not reconnecting after the server is moved to the next server or if one of the servers is shutoff and restarted. The customer started experiencing this adapter reconnection problem in their old 4.0 cluster environment using GIS WebSphere MQ Adapters only after they upgraded their Websphere MQ MSCS cluster server from 6.0.1.2 to 6.0.2.8. They also can recreate this reconnection problem using their GIS cluster at build 4319+hotfixes.

Error Message

[2010-02-24 18:32:05.705] ERROR 000000000000 GLOBAL_SCOPE <WebSphereMQServerImpl-18944148> MQException in doRcv: reasonCode=2202
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2202
at com.ibm.mq.MQQueue.get(MQQueue.java:1041)
at com.sterlingcommerce.woodstock.services.websphereMQ.WebSphereMQServerImpl.doRcv( WebSphereMQServerImpl.java:319)
at com.sterlingcommerce.woodstock.services.websphereMQ.WMQAsyncThread.run(WMQAsyncT hread.java:58)

[2010-02-24 18:32:05.861] ERROR 000000000000 GLOBAL_SCOPE <WebSphereMQServerImpl-29859736> MQException in doRcv: reasonCode=2162
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2162
at com.ibm.mq.MQQueue.get(MQQueue.java:1041)
at com.sterlingcommerce.woodstock.services.websphereMQ.WebSphereMQServerImpl.doRcv( WebSphereMQServerImpl.java:319)
at com.sterlingcommerce.woodstock.services.websphereMQ.WMQAsyncThread.run(WMQAsyncT hread.java:58)

[2010-02-24 18:32:05.861] ERROR 000000000000 GLOBAL_SCOPE <WebSphereMQServerImpl-859736> Exception during backout
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueueManager.backout(MQQueueManager.java:2326)
at com.sterlingcommerce.woodstock.services.websphereMQ.WebSphereMQServerImpl.doRcv( WebSphereMQServerImpl.java:495)
at com.sterlingcommerce.woodstock.services.websphereMQ.WMQAsyncThread.run(WMQAsyncT hread.java:58)

Resolving The Problem

Fix resolves this reported reconnection issue that started only after an upgrade of WSMQ Server from version 6.0.1.2 to 6.0.2.8. This was a MSCS Cluster server environment. With this fix applied, the GIS WebSphere MQ adapters will now handle the response error code 2009 properly

Please apply Gentran Integration Suite, Release 4.3 Build 4324 or later.

Please apply Sterling Integrator Release, Release 5.0 Build 5008 or later.

[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

NFX8479

Product Synonym

[<p><b>]Function Area[</b><p>];Adapters - WebSphereMQ;[<p><b>]Escalation ID[</b><p>];139301;[<p><b>]Fix ID[</b><p>];215587, 226687;[<p><b>]Severity[</b><p>];Critical;[<p><b>]Type[</b><p>];NormalFix;[<p><b>]Build[</b><p>];4324, 5008

Document Information

Modified date:
06 December 2019

UID

swg21553579