IBM Support

PI18511: WHEN MQ SERVER IS A BUS MEMBER AND CORRELLATIONID OF THE MESSAGE IS USED, QUEUE IS BROWSED AGAINST ALL MESSAGES.

Fixes are available

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In WebSphere Application Server (WAS), the MQ server is a
    member of the WAS bus.
    
    When a JMS consumer tries to consume a specific message from an
    MQ Queue using the correlationID of the message, the queue is
    still browsed against all the messages even though the
    appropriate Correlation ID index exists.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for                                         *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a WebSphere Application Server       *
    *                      environment where we have MQ as bus     *
    *                      member (PEV setup), When a jms          *
    *                      consumer attempts to consume a          *
    *                      specific message from MQ Queue using    *
    *                      correlationID of the message, the       *
    *                      queue is still browsed against all      *
    *                      the messages even though the            *
    *                      appropriate Correlation ID index        *
    *                      exists in the MQ.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a WebSphere Application Server environment where we have MQ
    as bus member (PEV setup), When a jms consumer attempts to
    consume a specific message from MQ Queue using correlationID
    of the message, the queue is still browsed against all the
    messages even though the appropriate Correlation ID index
    exists in the MQ.
    However, if the consumer directly connects to MQ queue and
    requests for a message with the correlation id, the message is
    immediately retrieved. In the traces, we observed that the
    correlation id is lost while processing the request and is not
    set on the MQGET command.
    

Problem conclusion

  • The solution is to check if correlation id is provided as
    selection criteria, if yes, then set the property on the MQ
    request so that MQ understands that the selection criteria is
    the correlation id of the message.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.37, 8.0.0.10, 8.5.5.4.  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

    PI18511

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-22

  • Closed date

    2014-09-05

  • Last modified date

    2014-09-05

  • 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

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PI18511

Modified date: 05 September 2014