IBM Support

PH03767: QMGR SENT AN UNEXPECTED MESSAGE TO CLIENT WHEN THE WAIT INTERVALFOR A BROWSE FIRST EXPIRES, RESULTS IN CONNECTION DISCONNECT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An unexpected message being sent to the client when the wait
    interval for a browse first expires at the same time as a
    matching message arrives on the queue. Client tried to copy the
    message, and if it doesn't fit to application buffer, then
    ArrayIndexOutofBounds Exception occurs. It causes client
    connection to disconnect and CSQX209E is seen on CHINIT JOBLOG.
    .
    Additional Symptom(s) Search Keyword(s):
    MQJE001 2009 MQRC_CONNECTION_BROKEN
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 8       *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Errors occur in client applications     *
    *                      using MQGMO_BROWSE_FIRST and MQGMO_WAIT *
    *                      if messages arrive as the wait interval *
    *                      expires.                                *
    *                      MQ Java clients encounter an            *
    *                      ArrayIndexOutofBounds exception,        *
    *                      causing the channel to terminate.       *
    *                      MQ C clients can return a message other *
    *                      than the first on the queue.            *
    ****************************************************************
    An MQ client issues a request for messages, causing the channel
    initiator to establish a callback to wait for messages.
    When the WaitInterval expires, the client issues another request
    for a message, requesting a notification when it has been sent.
    
    If multiple messages arrive as this notification is sent, a
    serialisation error in updating the browse state of the consumer
    can result in both the consumer thread and the receive thread
    sending a message to the client between the 2nd message request
    and the notification.
    This is not expected by the client, leading to incorrect
    behaviour with symptoms that vary depending on the client
    implementation.
    

Problem conclusion

  • The serialisation error relating to the browse state of the
    consumer is corrected, preventing the 2nd message being sent
    under these circumstances.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH03767

  • Reported component name

    IBM MQ Z/OS V8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-08

  • Closed date

    2018-11-15

  • Last modified date

    2019-01-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PH04226 UI59738

Modules/Macros

  • CMQXRSTF
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI59738

       UP18/12/14 P F812

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 January 2019