Fixes are available
WebSphere MQ V7.5 Fix Pack 7.5.0.3
Fix Pack 7.1.0.5 for WebSphere MQ V7.1
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.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
After upgrading the WebSphere MQ classes for Java level to 7.0.1.10, the following exception is being received by the application which is requesting a message from a WebSphere MQ queue located on a z/OS system: 02:00:46,571 WARN [ACSIP.P0A04152#1] WaitError: P0A04152: MQJE001: Completion Code '2', Reason '2247'.; - nested throwable: (com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2247'.) ... ... ... Caused by: com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2247'. at com.ibm.mq.MQDestination.getInt(MQDestination.java:666) at com.ibm.mq.MQDestination.get(MQDestination.java:519) ... ... ... The message is not received by the application.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ classes for Java who are requesting messages from a WebSphere MQ z/OS Queue Manager, where the receiving application is specifying either or both of the MQGetMessageOptions options: MQGMO_LOGICAL_ORDER MQGMO_ALL_MSGS_AVAILABLE Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: When receiving a message with the WebSphere MQ classes for Java API without specifying a maximum message size, using the method call: com.ibm.mq.MQDestination.get(MQMessage msg, MQGetMessageOptions gmo) internally within the WebSphere MQ classes for Java the MQGET operation may be broken into multiple stages, if the size of the message is larger than a predetermined value, before the message is received and passed back to the calling application. The WebSphere MQ classes for Java/JMS code change made under APAR IV30481, included in WebSphere MQ versions: 7.0.1.10 7.1.0.3 7.5.0.1 changed the behaviour of this multi-stage internal MQGET, such that the MQGMO option: 'MQMO_MATCH_MSG_TOKEN' was used to uniquely identify the message on the queue after the initial MQGET operation failed with a reason code MQRC 2080 'MQRC_TRUNCATED_MSG_FAILED' to indicate that the internal buffer size used by the WebSphere MQ classes for Java was too small to contain the message. When this change was used in combination with either the application specified GetMessageOptions (GMO): MQGMO_LOGICAL_ORDER and/or MQGMO_ALL_MSGS_AVAILABLE and the message was being consumed from a z/OS WebSphere MQ Queue Manager, where the queue was indexed by groupid, the queue manager returned a failure reason code: MQRC 2247 'MQRC_MATCH_OPTIONS_ERROR' which was in turn returned to the application. The GMO option 'MQGMO_MATCH_MSG_TOKEN' is not compatible with an MQGET call to a z/OS queue manager where the queue has been indexed by groupid.
Problem conclusion
The WebSphere MQ classes for Java have been modified to remove the GMO options: MQGMO_LOGICAL_ORDER MQGMO_ALL_MSGS_AVAILABLE prior to calling the second stage MQGET when the GMO option: MQMO_MATCH_MSG_TOKEN is in use. | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0010 | | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0010 | | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0010 | | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0010 | | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0010 | | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0010 | | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0010 | | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0010 | | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0010 | | MDVREGR 7.0.1-WS-MQ-Windows-FP0010 | | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0011 | | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0011 | | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0011 | | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0011 | | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0011 | | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0011 | | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0011 | | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0011 | | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0011 | | MDVREGR 7.0.1-WS-MQ-Windows-FP0011 | | MDVREGR 7.1.0-WS-MQ-AixPPC64-FP0003 | | MDVREGR 7.1.0-WS-MQ-HpuxIA64-FP0003 | | MDVREGR 7.1.0-WS-MQ-HpuxPaRISC64-FP0003 | | MDVREGR 7.1.0-WS-MQ-LinuxIA32-FP0003 | | MDVREGR 7.1.0-WS-MQ-LinuxPPC64-FP0003 | | MDVREGR 7.1.0-WS-MQ-LinuxS390X-FP0003 | | MDVREGR 7.1.0-WS-MQ-LinuxX64-FP0003 | | MDVREGR 7.1.0-WS-MQ-SolarisSparc64-FP0003 | | MDVREGR 7.1.0-WS-MQ-SolarisX64-FP0003 | | MDVREGR 7.1.0-WS-MQ-Windows-FP0003 | | MDVREGR 7.1.0-WS-MQ-AixPPC64-FP0004 | | MDVREGR 7.1.0-WS-MQ-HpuxIA64-FP0004 | | MDVREGR 7.1.0-WS-MQ-HpuxPaRISC64-FP0004 | | MDVREGR 7.1.0-WS-MQ-LinuxIA32-FP0004 | | MDVREGR 7.1.0-WS-MQ-LinuxPPC64-FP0004 | | MDVREGR 7.1.0-WS-MQ-LinuxS390X-FP0004 | | MDVREGR 7.1.0-WS-MQ-LinuxX64-FP0004 | | MDVREGR 7.1.0-WS-MQ-SolarisSparc64-FP0004 | | MDVREGR 7.1.0-WS-MQ-SolarisX64-FP0004 | | MDVREGR 7.1.0-WS-MQ-Windows-FP0004 | | MDVREGR 7.5.0-WS-MQ-AixPPC64-FP0001 | | MDVREGR 7.5.0-WS-MQ-HpuxIA64-FP0001 | | MDVREGR 7.5.0-WS-MQ-HpuxPaRISC64-FP0001 | | MDVREGR 7.5.0-WS-MQ-LinuxIA32-FP0001 | | MDVREGR 7.5.0-WS-MQ-LinuxPPC64-FP0001 | | MDVREGR 7.5.0-WS-MQ-LinuxS390X-FP0001 | | MDVREGR 7.5.0-WS-MQ-LinuxX64-FP0001 | | MDVREGR 7.5.0-WS-MQ-SolarisSparc64-FP0001 | | MDVREGR 7.5.0-WS-MQ-SolarisX64-FP0001 | | MDVREGR 7.5.0-WS-MQ-Windows-FP0001 | | MDVREGR 7.5.0-WS-MQ-AixPPC64-FP0002 | | MDVREGR 7.5.0-WS-MQ-HpuxIA64-FP0002 | | MDVREGR 7.5.0-WS-MQ-HpuxPaRISC64-FP0002 | | MDVREGR 7.5.0-WS-MQ-LinuxIA32-FP0002 | | MDVREGR 7.5.0-WS-MQ-LinuxPPC64-FP0002 | | MDVREGR 7.5.0-WS-MQ-LinuxS390X-FP0002 | | MDVREGR 7.5.0-WS-MQ-LinuxX64-FP0002 | | MDVREGR 7.5.0-WS-MQ-SolarisSparc64-FP0002 | | MDVREGR 7.5.0-WS-MQ-SolarisX64-FP0002 | | MDVREGR 7.5.0-WS-MQ-Windows-FP0002 | --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.13 v7.1 7.1.0.5 v7.5 7.5.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
IC97121
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-10-23
Closed date
2013-10-31
Last modified date
2014-03-21
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 WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R701 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 April 2022