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

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?