IBM Support

IT08256: WEBSPHERE MQ ADAPTERS ARE DISABLED AFTER A WINDOWS HOST CLUSTER FAILOVER WHICH HOSTS THE WEBSPHERE MQ SERVER.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When the Windows server that hosts WebSphere MQ server fails
    over to a different Windows Server some of the Sterling B2B
    Integrator WebSphere MQ adapters are disabled and need to be
    manually re-enabled.
    
    system.log
    ERROR 000000000000 GLOBAL_SCOPE
    <WebSphereMQServerImpl-wsmq_sample_adapter_name_async--955776797
    > MQException while moving to backout queue, So backing out
    com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason
    '2009'.
    at com.ibm.mq.MQQueueManager.backout(MQQueueManager.java:1754)
    at
    com.sterlingcommerce.woodstock.services.websphereMQ.WebSphereMQS
    erverImpl.backout_message(WebSphereMQServerImpl.java:848)
    at
    com.sterlingcommerce.woodstock.services.websphereMQ.WebSphereMQS
    erverImpl.doRcv(WebSphereMQServerImpl.java:522)
    at
    com.sterlingcommerce.woodstock.services.websphereMQ.WMQAsyncThre
    ad.run(WMQAsyncThread.java:50)
    Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009
    at
    com.ibm.mq.jmqi.remote.impl.RemoteSession.getConnection(RemoteSe
    ssion.java:509)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteSession.allocateMQAPI(RemoteSe
    ssion.java:1375)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteSession.allocateMQAPI(RemoteSe
    ssion.java:1345)
    at
    com.ibm.mq.jmqi.remote.api.RemoteFAP.MQBACK(RemoteFAP.java:9739)
    at
    com.ibm.mq.jmqi.monitoring.JmqiInterceptAdapter.MQBACK(JmqiInter
    ceptAdapter.java:113)
    at com.ibm.mq.MQSESSION.MQBACK(MQSESSION.java:743)
    at com.ibm.mq.MQQueueManager.backout(MQQueueManager.java:1751)
    ... 3 more
    Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9213:
    A communications error for 'TCP' occurred.
    [1=java.net.SocketException[Connection
    reset],4=TCP,5=sockInStream.read]
    at
    com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.receive(RemoteTC
    PConnection.java:1555)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.receiveBuffer(Remote
    RcvThread.java:794)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.receiveOneTSH(Remote
    RcvThread.java:757)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.run(RemoteRcvThread.
    java:150)
    at java.lang.Thread.run(Thread.java:781)
    Caused by: java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:189)
    at java.net.SocketInputStream.read(SocketInputStream.java:121)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.receive(RemoteTC
    PConnection.java:1545)
    ... 4 more
    

Local fix

  • STRRTC - 46235
    SB/SB
    
    Circumvention:
    Restart Sterling B2B Integrator to reenable the WSMQ adapters.
    

Problem summary

  • Users Affected:
    WSMQ Adapter Users
    
    Problem Description:
    Windows OS cluster fails over that hosts WSMQ server. This
    disabled WSMQ adapters in Sterling B2B Integrator until a
    restart is performed.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    The WSMQ adapters now go into retry mode for the number of retry
    attempts set in the service def pafe whenever the WSMQ queue
    manager is shut down. During this retry interval, if the Queue
    Manager comes back, then it is possible to receive files without
    restarting the adapter.
    
    Delivered In:
    5020500_4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT08256

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    525

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-04-13

  • Closed date

    2015-04-23

  • Last modified date

    2015-04-29

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R525 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.5","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
29 April 2015