Direct links to fixes
APAR status
Closed as program error.
Error description
WebSphere MQ Get Service picks up all messages for one correlation ID only and the messages related to other correlation IDs are ignored. If the queue has 5 messages, 3 messages grouped by correlation identifier TEST123 and 2 messages grouped by correlation identifier TEST890, then the WebSphere MQ Get Service picks up 3 messages for correlation identifier TEST123 and put them in process data. But the other 2 messages grouped by correlation identifier TEST890 are not picked up. It is not able to get the next logical group messages, before it throws MQRC_NO_MSG_AVAILABLE and completes the action, instead of fetching the next set of messages. It could be a limitation in MQ GET service itself where MQMessage.get() does not fetch the new set unless it is re-initialized. Once all messages of the 1st set of correlation IDs are fetched, it throws QRC_NO_MSG_AVAILABLE and the next set of messages are not picked up with MQMEssage.get(msg,gmo).
Local fix
Problem summary
USERS AFFECTED: WebSphere MQ users PROBLEM DESCRIPTION: WebSphere MQ Get Service picks up all messages for one correlation ID only and the messages related to other correlation IDs are ignored. If the queue has 5 messages, 3 messages grouped by correlation identifier TEST123 and 2 messages grouped by correlation identifier TEST890, then the WebSphere MQ Get Service picks up 3 messages for correlation identifier TEST123 and put them in process data. But the other 2 messages grouped by correlation identifier TEST890 are not picked up. It is not able to get the next logical group messages, before it throws MQRC_NO_MSG_AVAILABLE and completes the action, instead of fetching the next set of messages. It could be a limitation in MQ GET service itself where MQMessage.get() does not fetch the new set unless it is re-initialized. Once all messages of the 1st set of correlation IDs are fetched, it throws QRC_NO_MSG_AVAILABLE and the next set of messages are not picked up with MQMEssage.get(msg,gmo). PLATFORMS AFFECTED: All
Problem conclusion
RESOLUTION SUMMARY: A code fix is provided. DELIVERED IN: 5020600 5020500_11 5020601_2
Temporary fix
Comments
APAR Information
APAR number
IT00670
Reported component name
STR B2B INTEGRA
Reported component ID
5725D0600
Reported release
524
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-03-28
Closed date
2015-10-14
Last modified date
2016-04-11
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
STR B2B INTEGRA
Fixed component ID
5725D0600
Applicable component levels
R526 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.4","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
11 April 2016