IBM Support

PH26694: AN MDB BOUND TO MQ VIA A LISTENER PORT STOPS CONSUMING MESSAGES AFTER AN MQRC_CONNECTION_BROKEN ERROR.

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

  • A Message Driven Bean bound against MQ JMS provider using a
    listener port fails to consume anymore messages after
    receiving a connection error.
    
    The following errors are logged in the WebSphere SystemOut.log:
    
    CWSJY0003W: JMSCC3036: An exception has been delivered to the
    connection's exception listener: '
    Message : com.ibm.msg.client.jms.DetailedJMSException:
    JMSWMQ1107: A problem with this connection has occurred.
    An error has occurred with the WebSphere MQ JMS connection.
    Use the linked exception to determine the cause of this error.
    Caused by [1]
    --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ
    call failed with compcode '2' ('MQCC_FAILED') reason '2009'
    ('MQRC_CONNECTION_BROKEN').
    Class : class com.ibm.mq.MQException
    Stack :
    com.ibm.msg.client.wmq.common.internal.Reason.createException(Re
    ason.java:204)
    :
    com.ibm.msg.client.wmq.internal.WMQConnection.consumer(WMQConnec
    tion.java:814)
    : com.ibm.mq.jmqi.remote.api.RemoteHconn.callEventHandler(Remo
    teHconn.java:2648)
    :
    com.ibm.mq.jmqi.remote.api.RemoteHconn.driveEventsEH(RemoteHconn
    .java:571)
    ...
    J2CA0056I: The Connection Manager received a fatal connection
    error from the Resource Adapter for resource XXXQCF. The
    exception is:
    com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ1107: A
    problem with this connection has occurred.
    An error has occurred with the WebSphere MQ JMS connection.
    Use the linked exception to determine the cause of this
    error.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call
    failed with compcode '2' ('MQCC_FAILED') reason '2009'
    ('MQRC_CONNECTION_BROKEN').
    .... ... ...
    Caused by [3] -->
    Message : com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9208:
    Error on receive from host 'XXX/ipaddress:port (XXXhost)'.
    [1=-1,2=ffffffff,3=XXXhost/host:port (host),4=TCP]
    
    The listener port remains running but cannot process any
    messages, generating the J2CA0027E, WTRN0078E and J2CA0030E
    error messages, for example:
    
    J2CA0027E: An exception occurred while invoking start on an XA
    Resource Adapter from DataSource XXX MQ
    ConnectionFactory$JMSManagedConnection@11, within transaction ID
    {XidImpl: formatId(57415344), gtrid_length(36), bqual_length(54)
    ,
    data(00000172b96d9a2f00000001657706c0828b32bd1f95db5f1713f33c8
    b3ee9a989800a4e00000172b96d9a2f00000001657706c0828b32bd1f95db5f1
    713f33c8b3ee9a989800a4e000000010000000000000000000000000001)} :
    javax.transaction.xa.XAException: The method 'xa_start' has
    failed with errorCode '-7'.
    at com.ibm.mq.jmqi.JmqiXAResource.start(JmqiXAResource.java:924)
    at
    com.ibm.ejs.jms.JMSManagedSession$JMSXAResource.start(JMSManaged
    Session.java:1140)
    at
    com.ibm.ejs.j2c.XATransactionWrapper.start(XATransactionWrapper.
    java:14
    79)
    ...
    at com.ibm.ws.tx.jta.TransactionImpl.enlistResource(TransactionI
    mpl.java:2270)
    ..........
    
    WTRN0078E: An attempt by the transaction manager to call start
    on a transactional resource has resulted in an error. The error
    code was XAER_RMFAIL. The exception stack trace follows:
    javax.transaction.xa.XAException: The method 'xa_start' has
    failed with errorCode '-7'.
    at com.ibm.mq.jmqi.JmqiXAResource.start(JmqiXAResource.java:924)
    at
    com.ibm.ejs.jms.JMSManagedSession$JMSXAResource.start(JMSManaged
    Session.java:1140)
    at
    com.ibm.ejs.j2c.XATransactionWrapper.start(XATransactionWrapper.
    java:1479)
    at com.ibm.ws.Transaction.JTA.JTAResourceBase.start(JTAReso
    urceBase.java:157)
    .....
    
    
    J2CA0030E: Method enlist caught
    javax.transaction.SystemException: XAResource start association
    error:XAER_RMFAIL
    at
    com.ibm.tx.jta.impl.RegisteredResources.startRes(RegisteredResou
    rces.java:1088)
    at
    com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredR
    esources.java:1161)
    ...
    Caused by: javax.transaction.xa.XAException: The method
    'xa_start' has failed with errorCode '-7'.
    at com.ibm.mq.jmqi.JmqiXAResource.start(JmqiXAResource.java:924)
    at
    com.ibm.ejs.jms.JMSManagedSession$JMSXAResource.start(JMSManaged
    Session.java:1140)
    ...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of the   *
    *                  WebSphere MQ JMS Provider                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The WebSphere Application Server may    *
    *                      not correctly identify JMS Exceptions   *
    *                      as connection errors.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a message driven bean fails to consume messages from
    WebSphere MQ due to a network connection error, the WebSphere
    Application Server messaging component does not identify
    the Exception as a connection error in some cases.
    

Problem conclusion

  • The WebSphere Application Server messaging component was
    modified to correctly identify the condition as a connection
    error.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.19 and 9.0.5.6. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH26694

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-22

  • Closed date

    2020-10-12

  • Last modified date

    2020-10-12

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
13 October 2020