Fixes are available
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
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
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
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
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
MismatchedMessageStoreException occurs after WebSphere Application Server is restarted.The following error is logged in the SystemOut.log for the server hosting the Service Integration Bus Messaging Engine: CWSIP0002E: An internal messaging error occurred in com.ibm. ws.sib.processor.impl.ConsumerDispatcher, 1:745:1.280.5.15, com.ibm.ws.sib.msgstore.MismatchedMessageStoreException: Transaction supplied on add does not originate from this MessageStore! MS: com.ibm.ws.sib.msgstore.impl.MessageStore Impl@30dd30dd[State:Started], Tran.MS: com.ibm.ws.sib. msgstore.impl.MessageStoreImpl@6c796c79[State:Started] FFDC produced has the following stack: at com.ibm.ws.sib.processor.impl.store.items.MessageItem. beforeCompletion(MessageItem.java:2138) at com.ibm.ws.sib.msgstore.transactions.XidParticipant. prepare(XidParticipant.java:311) at com.ibm.ws.sib.msgstore.transactions.XidManager.prepare (XidManager.java:297) at com.ibm.ws.sib.msgstore.transactions.MSDelegatingXA Resource.prepare(MSDelegatingXAResource.java:410) at com.ibm.ws.sib.api.jmsra.impl.JmsJcaRecoverableSiXa Resource.prepare(JmsJcaRecoverableSiXaResource.java:248) at com.ibm.ejs.j2c.XATransactionWrapper.prepare(XA TransactionWrapper.java:1129) at com.ibm.tx.jta.JTAXAResourceImpl.prepare(JTAXAResource Impl.java:224) ..... at com.ibm.ws.sib.processor.impl.ConsumerDispatcher.store Message(ConsumerDispatcher.java:751) at com.ibm.ws.sib.processor.impl.ConsumerDispatcher.put (ConsumerDispatcher.java:903) at com.ibm.ws.sib.processor.impl.PtoPInputHandler.eventPre commitAdd(PtoPInputHandler.java:1320) at com.ibm.ws.sib.processor.impl.PtoPInputHandler.message EventOccurred(PtoPInputHandler.java:1233) at com.ibm.ws.sib.processor.impl.store.items.MessageItem. beforeCompletion(MessageItem.java:2116) . at com.ibm.ws.sib.msgstore.cache.links.ItemStreamLink. addItem(ItemStreamLink.java:321) at com.ibm.ws.sib.msgstore.ItemStream.addItem(Item Stream.java:115) at com.ibm.ws.sib.msgstore.ItemStream.addItem(ItemStream. java:146) at com.ibm.ws.sib.processor.impl.ConsumerDispatcher.store Message(ConsumerDispatcher.java:720)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server Version 7.0* **************************************************************** * PROBLEM DESCRIPTION: MismatchedMessageStoreException, or * * XAException with error code * * XAER_NOTA, when committing a * * transaction * **************************************************************** * RECOMMENDATION: * **************************************************************** The default messaging provider code incorrectly allows the messaging engine connection passed to the transaction manager (in a JmsJcaSessionImpl object) to be connected to a different messaging engine to the connection used when performing the sends/receives (in a JmsSessionImpl object). The problem occurs when the JMS connection obtains its connection to the messaging engine from the connection pool, rather than creating a new connection. This connection is used when performing sends/receives etc. for any session created from that connection, and also should provide a model for all connections created for transaction coordination of individual sessions. However, the code incorrectly fails to store a reference to the connection in the correct place for it to be used as the model for creating messaging engine connections for transaction coordination. This means the connection passed to the transaction manager to control the transaction of a session might be connected to a different messaging engine, which then rejects the attempt to prepare/commit/rollback the transaction. The problem is most likely to occur when multiple messaging engines for the same bus are running in a single JVM, and the application is running locally within that same JVM.
Problem conclusion
The fix for this APAR ensures that when a JMS connection obtains its messaging engine connection from an existing connection in the pool, it stores it in the correct place to be used as a model for creation of connections for transaction coordination of individual sessions using that connection. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.11. 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
PM07867
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-18
Closed date
2010-03-12
Last modified date
2010-03-12
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
620800101
Applicable component levels
R300 PSY
UP
Document Information
Modified date:
24 October 2021