IBM Support

PM20805: MESSAGES NOT DELIVERED TO MDB AFTER THE WMQ CHANNEL INTITATOR IS RESTARTED, AND CWSJP0002E ERRORS ARE LOGGED BY THE BUS

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If the channel initiator is restarted on a WebSphere MQ zOS
    queue manager, an MDB processing messages via a WebSphere MQ
    Server Service Integration Bus member is not delivered any
    more messages after the restart.
    
    The following exception is reported in the WebSphere
    Application ServerS ystemOut logs
    com.ibm.ws.sib.remote.mq.exceptions.CorruptRMQSessionException:
    CWSJP0002E:An internal messaging error occurred in
    
    com.ibm.ws.sib.remote.mq.impl.AbstractRMQSession, 1:968:1.71.1.2
    due to an exception com.ibm.mq.MQException: MQJE001:
    Completion Code '2' Reason '2009'
    .
    FFDCs are also recorded with the following
    .
    com.ibm.ws.sib.processor.impl.exceptions.RMQSessionDroppedExcept
    ion:
    CWSIP0815W: A message could not be received from destination
    QBIT100 assigned to WebSphere MQ Server bus member F4D291566880E
    69C. The WebSphere MQ completion code was 2. The WebSphere MQ
    reason code was 2009.
    at com.ibm.ws.sib.processor.impl.mqproxy.RMQCursor.
    

Local fix

  • A restart of the application is needed to begin processing messa
    ges again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server Version    *
    *                  7.0, with WebSphere MQ Server bus members   *
    ****************************************************************
    * PROBLEM DESCRIPTION: MDB stops receiving messages, due to    *
    *                      a deadlock, after losing connectivity   *
    *                      to a WebSphere MQ Server bus member     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A javacore from the messaging engine shows a thread calling
    com.ibm.ws.sib.processor.impl.RMQConsumerKey.
                                     closeLocalisationUnreachable()
    from within method
    com.ibm.ws.sib.processor.impl.RMQAsynchThread.
                                                runAsynchConsumer()
    
    This thread is deadlocked, because it is waiting for itself to
    complete. The deadlock prevents the messaging engine from
    handling the broken connection to the queue manager, and no
    further messages are delivered to the MDB.
    
    The thread waits for itself because an incorrect value of an
    internal state variable in the RMQAsynchThread object.
    

Problem conclusion

  • The fix for this APAR corrects the state of the
    RMQAsynchThread object, so that it does not deadlock when the
    connection to the queue manager is lost, and it informs the
    MDB endpoint of the broken connection (so that it can perform
    its regular recovery logic to reconnect to the queue when it
    becomes available again).
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM20805

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-18

  • Closed date

    2010-10-26

  • Last modified date

    2010-10-26

  • 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

    PLAT MSG COM

  • Fixed component ID

    620800101

Applicable component levels

  • R300 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM20805

Modified date: 26 October 2010