Fixes are available
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 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
APAR status
Closed as program error.
Error description
WebSphere MQ queue managers may be added as bus members in the WebSphere Application Server administrative console; z/OS queue managers are allowed in WSAS 6.1 while WSAS 7.0 allows other platforms. In such an environment a Service Integration Bus alias destination may point to a destination on the WebSphere MQ Server bus member. If an application is producing messages to a WebSphere MQ Server bus member through a SIB alias under a transaction, and the connection to the WebSphere MQ queue manager is broken, it is possible for the message to be lost. The transaction branch involving WebSphere MQ completes with an XA_RDONLY return code rather than XA_RBROLLBACK, which allows the transaction to commit even if the message was not successfully placed on the WebSphere MQ queue. When this problem occurs, an ffdc will be generated showing a com.ibm.websphere.sib.exception.SIErrorException with a ProbeId of 1 reported by com.ibm.ws.sib.transactions.impl. TransactionCallbackTable$TransactionCallbackWrapper in method com.ibm.ws.sib.transactions.impl.TransactionCallbackTable. beforeCompletion(). The ffdc may also show: . com.ibm.websphere.sib.exception.SIErrorException: com.ibm.ws.sib.processor.impl.exceptions.RMQResourceException: CWSIP0002E: An internal messaging error occurred in com.ibm.ws.sib.processor.impl.mqproxy.RMQSessionManager, 1:609:1.44, com.ibm.ws.sib.remote.mq.exceptions. CorruptRMQSessionException: CWSJP0024E: A Websphere MQ error was encountered when using the Websphere MQ queue manager ?X?: com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2009'. @ com.ibm.ws.sib.processor.impl.store.items.MessageItem. beforeCompletion(MessageItem.java:2138) com.ibm.ws.sib.transactions.impl.TransactionCallbackTable$ TransactionCallbackWrapper.beforeCompletion (TransactionCallbackTable.java:101) com.ibm.ws.sib.transactions.impl.TransactionCallbackTable. beforeCompletion(TransactionCallbackTable.java:253) com.ibm.ws.sib.transactions.impl. XAResourceWithSubordinatesImpl.end (XAResourceWithSubordinatesImpl.java:266) com.ibm.ws.sib.comms.server.IdToTransactionTable$ $ResourceManagerEntry.endCurrentTransactionBranch (IdToTransactionTable.java:979) com.ibm.ws.sib.comms.server.IdToTransactionTable. endOptimizedGlobalTransactionBranch (IdToTransactionTable.java:629) com.ibm.ws.sib.comms.server.clientsupport. StaticCATXATransaction.rcvXAPrepare (StaticCATXATransaction.java:483) com.ibm.ws.sib.comms.server.clientsupport. ServerTransportReceiveListener.dataReceived (ServerTransportReceiveListener.java:355) com.ibm.ws.sib.jfapchannel.impl.rldispatcher. ConversationReceiveListenerDataReceivedInvocation.invoke (ConversationReceiveListenerDataReceivedInvocation.java:195) com.ibm.ws.sib.jfapchannel.impl.rldispatcher. ReceiveListenerDispatchQueue.run (ReceiveListenerDispatchQueue.java:542) com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550) Caused by: com.ibm.ws.sib.processor.impl.exceptions.RMQResourceException: CWSIP0002E: An internal messaging error occurred in com.ibm.ws.sib.processor.impl.mqproxy.RMQSessionManager, 1:609:1.44, com.ibm.ws.sib.remote.mq.exceptions. CorruptRMQSessionException: CWSJP0024E: A WebSphere MQ error was encountered when using the Websphere MQ queue manager ?X?: com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2009'. @ com.ibm.ws.sib.processor.impl.mqproxy.RMQSessionManager. getSession(RMQSessionManager.java:605) com.ibm.ws.sib.processor.impl.mqproxy.MQLocalization. getRMQSession(MQLocalization.java:225) com.ibm.ws.sib.processor.impl.mqproxy.MQLocalization.put (MQLocalization.java:587) com.ibm.ws.sib.processor.impl.RMQConsumerManager.put (RMQConsumerManager.java:1237) com.ibm.ws.sib.processor.impl.PtoPInputHandler. eventPrecommitAdd(PtoPInputHandler.java:1322) com.ibm.ws.sib.processor.impl.PtoPInputHandler. messageEventOccurred(PtoPInputHandler.java:1235) com.ibm.ws.sib.processor.impl.store.items.MessageItem. beforeCompletion(MessageItem.java:2116) ...
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server Version 7.0* * with IBM WebSphere MQ Server bus members * **************************************************************** * PROBLEM DESCRIPTION: Persistent messages might be lost when * * sending to a WebSphere MQ Server queue * * via an alias destination, within a * * transaction, when the queue manager * * is unavailable. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem only affects sends of messages to WebSphere MQ Server queues, via a Service Integration Bus alias destination. Transactions incorrectly commit, even though the send of a persistent message is attempted to a WebSphere MQ Server bus member when the queue manager is unavailable. When an alias destination is used, the messaging engine only detects that the queue manager is unavailable during completion of the transaction, when it attempts to persist the message to the WebSphere MQ queue. The problem occurs because the messaging engine fails to report the error to the transaction manager. Instead of reporting a suitable error code, it returns a success return code of XA_RDONLY, incorrectly indicating that no work was performed by the application.
Problem conclusion
The fix for this APAR changes the messaging engine to correctly report the failure to the transaction manager, so that the complete transaction is rolled back. For example, if the failed send was performed within an MDB consuming another message, then the other message would be rolled back onto the queue (rather than deleted). The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.15. 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
PM23837
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-04
Closed date
2010-12-02
Last modified date
2010-12-02
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
PLAT MSG COM
Fixed component ID
620600101
Applicable component levels
R200 PSY
UP
Document Information
Modified date:
24 October 2021