IBM Support

IV70660: A REBROWSE FAILS WITH 2033 (MQRC_NO_MSG_AVAILABLE), WHICH CAUSES A JMSEXCEPTION TO BE GENERATED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using a WebSphere Application Server Listener Port to
    browse for messages on a WebSphere MQ queue to deliver messages
    to an MDB application, the Listener Port logs the following
    exception in the Control Region job log:
    
    BBOO0221W: [:] CWSJY0003W: JMSWMQ0036: Application Server
    Facilities caught exception '
                           Message :
    com.ibm.msg.client.jms.DetailedIllegalStateException:
    JMSWMQ2002: Failed to get a message from destination 'MYQUEUE'.
    WebSphere MQ classes for JMS attempted to perform an MQGET;
    however WebSphere MQ reported an error.
    Use the linked exception to determine the cause of this error.
                             Class : class
    com.ibm.msg.client.jms.DetailedIllegalStateException
                             Stack :
    com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(
    Reason.java:474)
                                   :
    com.ibm.msg.client.wmq.common.internal.Reason.createException(Re
    ason.java:216)
                                   :
    com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCall
    Success(WMQMessageConsumer.java:124)
                                   :
    com.ibm.msg.client.wmq.internal.WMQConnectionBrowser$WMQConnecti
    onBrowserShadow.rebrowseMessage(WMQConnectionBrowser.java:1195)
                                   :
    com.ibm.msg.client.wmq.internal.WMQConnectionBrowser$WMQConnecti
    onBrowserShadow.browseHeaderData(WMQConnectionBrowser.java:1130)
                                   :
    com.ibm.msg.client.wmq.internal.WMQConnectionBrowser$WMQConnecti
    onBrowserShadow.consumer(WMQConnectionBrowser.java:752)
                                   :
    com.ibm.mq.jmqi.local.internal.LocalProxyConsumer.jmqiConsumerMe
    thod(LocalProxyConsumer.java:222)
         Caused by [1] --> Message : com.ibm.mq.MQException:
    JMSCMQ0001: WebSphere MQ call failed with compcode '2'
    ('MQCC_FAILED') reason '2033' ('MQRC_NO_MSG_AVAILABLE').
    
    When this exception occurred, the WebSphere Application Server
    Listener Port would stop and attempt to restart, as per the
    recovery processing that it has been configured with. The
    following is logged in the WebSphere Application Server Control
    Region job log:
    
    BBOJ0101I: MDB LISTENER STOPPED SUCCESSFULLY FOR MDB:
    MyEar#MyConsumerMdbjar#MyMDB, LISTENER PORT: MyListenerPort,
    DESTINATION: queue:///MYQUEUE
    
    BBOJ0102I: MDB LISTENER FOR MDB: MyEar#MyConsumerMdbjar#MyMDB,
    LISTENER PORT: MyListenerPort WILL ATTEMPT TO RESTART IN 60
    SECONDS. RECOVERY COUNT = 1.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere Application Server for z/OS V7 WebSphere MQ
    messaging provider.
    - The WebSphere Application Server for z/OS V8 WebSphere MQ
    messaging provider.
    - The WebSphere Application Server for z/OS V8.5 WebSphere MQ
    messaging provider.
    
    who have a message-driven bean (MDB) application configured
    against a WebSphere Application Server Listener Port.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a WebSphere Application Server Listener Port is active, it
    browses for messages on a WebSphere MQ queue in order to detect
    messages that can be delivered to a message-driven bean (MDB)
    application. For WebSphere Application Server for z/OS, a
    Listener Port browses the WebSphere MQ queue specifying a fix
    buffer size for the browsed message to be returned by the queue
    manager such that not all of the message payload is browsed, but
    just the WebSphere MQ messages headers.
    
    When a message was returned by the queue manager to the Listener
    Port that contained more WebSphere MQ message header data that
    could fit in the specified buffer, the Listener Port attempted
    to rebrowse the message on the queue specifying a buffer of
    increased size, enough to capture all of the WebSphere MQ
    messages header data. However, if the target message was no
    longer available on the queue for the rebrowse, for example
    because it had since been consumed by another consumer or the
    message had expired, the queue manager would return the
    WebSphere MQ reason code 2033 (MQRC_NO_MSG_AVAILABLE). When this
    occurred, the WebSphere MQ classes JMS generated a JMSException
    containing the 2033 reason code that was thrown back to the
    WebSphere Application Server Listener Port. This caused the
    WebSphere Application Server Listener Port to stop and initiate
    retry processing to reconnect to WebSphere MQ.
    

Problem conclusion

  • The WebSphere MQ classes for JMS have been updated such that a
    JMSException containing the WebSphere MQ reason code 2033
    (MQRC_NO_MSG_AVAILABLE) is not thrown to the browsing WebSphere
    Application Server Listener Port in the case a queue manager
    returns such an error after an attempt to rebrowse a message
    with a larger buffer.
    
    Should the queue manager return the WebSphere MQ reason code
    2033 in this scenario, then the listener port will attempt to
    deliver any messages previously browsed to the message-driven
    bean (MDB) application, up to the value configured by the
    Listener Port property "maximum messages", before returning to
    continue to browse the WebSphere MQ queue for more messages.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.7
    v7.5       7.5.0.6
    v8.0       8.0.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

    IV70660

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-03-06

  • Closed date

    2015-03-30

  • Last modified date

    2015-03-30

  • 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

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R710 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1"}]

Document Information

Modified date:
09 March 2021