What causes 'commit failed' errors to appear in the JMS server logs?
(Doc ID 1025243.1)
Last updated on APRIL 23, 2019
Applies to:Sun Schema Runtime Environment (SRE) - Version 5.0.5u2 and later
Information in this document applies to any platform.
Sun SeeBeyond Schema Runtime Environment (SRE) - Version: 5.0.5 and later
Checked for relevance on 14-APR-2013
What do the following messages from the JMS server logs indicate:
CheckTSList() failed : consumer or producer sessionid=2468298980,id=1 no longer exists
CommitAction::Execute() - commit failed txnid=2468303107
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document