APAR status
Closed as duplicate of another APAR.
Error description
An application encounters a poison message. The message should go to the backout queue ( BOQNAME on the queue definition ). Instead, it remains on the application queue. The application is not able to process subsequent messages on the queue. For bindings mode connections on z/OS, the processing to handle backout requeue of a message may incorrectly believe that the session state is suitable to commit the backout, but the session's transaction is being managed by WebSphere Application Server (WAS) using RRS. This results in MQRC_ENVIRONMENT_ERROR being returned on the MQCMIT call. The error in the WAS log is: com.ibm.msg.client.jms.DetailedJMSException.setLinkedException( Exception) (com.ibm.msg.client.jms.DetailedJMSException) ExtendedMessage: Entry; com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2012' ('MQRC_ENVIRONMENT_ERROR'). at com.ibm.msg.client.wmq.common.internal.Reason.createException (Reason.java:223) at com.ibm.msg.client.wmq.common.internal.Reason.createException (Reason.java:275) at com.ibm.msg.client.wmq.internal.WMQSession.syncpoint (WMQSession.java:1644) at com.ibm.msg.client.wmq.internal.WMQSession.commit (WMQSession.java:798) at com.ibm.msg.client.wmq.internal.WMQPoison.syncpoint (WMQPoison.java:739) at com.ibm.msg.client.wmq.internal.WMQPoison.handlePoisonMessage (WMQPoison.java:391) ... Additional Symptom(s) Search Keyword(s): BOQNAME JMSCMQ0001 WAS back out
Local fix
Delete the poison message and restart WebSphere Application Server
Problem summary
Problem conclusion
Temporary fix
Comments
Problem summary: A JMS application, running in WebSphere Application Server, uses a bindings mode JMS Connection to receive messages from MQ. At the time of the receive the application has a WSAS transaction in progress, so the MQ work is enlisted as part of the RRS global transaction. If the message received by the MQ JMS code has a backout count at or above the backout threshold defined on the MQ queue, the message will be handled as a poison message and will be requeued to the specified backout requeue queue. If no previous in-syncpoint work has been done by the JMS Session, then the poison message processing attempts to commit the requeue of the message. This is not valid while an RRS global transaction is in progress, so the MQCMIT call fails with reason code 2012 (MQRC_ENVIRONMENT_ERROR). com.ibm.msg.client.jms.DetailedJMSException: JMSCMQ0002: The method 'MQCMIT' failed. A WebSphere MQ call failed. Please see the linked exception for more information.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2012' ('MQRC_ENVIRONMENT_ERROR'). Problem resolution: The MQ JMS code has been updated so that it will not call MQCMIT while handling a poison message as part of an RRS global transaction. This fix changes the Java component of MQ, and will be included in a FixPack APAR. The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.12 (PM96878 on z/OS) v7.1 7.1.0.5 (PM96881 on z/OS) v7.5 7.5.0.3 (Distributed platforms only) 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
APAR Information
APAR number
PM89892
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
018
Status
CLOSED DUB
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-05-28
Closed date
2013-09-27
Last modified date
2014-03-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"7.0.1"}]
Document Information
Modified date:
06 September 2021