Transaction abort and timeout messages in JBoss EAP
Issue
The following warnings are reported during transaction processing:
-
EAP 6/7:
... WARN ... ARJUNA012117: TransactionReaper::check processing TX <xid> in state RUN ... WARN ... ARJUNA012095: Abort of action id <xid> invoked while multiple threads active within it. ... WARN ... ARJUNA012108: CheckedAction::check - atomic action <xid> aborting with 1 threads active! ... WARN ... ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX <xid>
NOTE: In EAP versions before 7.4.0,
ARJUNA012117
message will be output asTransactionReaper::check timeout for TX <xid> in state RUN
. -
EAP 5:
WARN ... - TransactionReaper::check timeout for TX <xid> in state RUN WARN ... - Abort of action id <xid> invoked while multiple threads active within it. WARN ... - CheckedAction::check - atomic action <xid> aborting with 1 threads active! WARN ... - TransactionReaper::doCancellations worker Thread[Thread-10,5,jboss] successfully canceled TX <xid>
-
EAP 4:
WARN ... - Abort of action id <xid> invoked while multiple threads active within it. WARN ... - CheckedAction::check - atomic action <xid> aborting with 1 threads active!
Note: <xid>
in the above represents the transaction id which will have the form of something like 7f000001:ece6:52ce0808:71
or 0:ffff7f000001:-1dde6ae2:52ccdf8c:b
- Following or nearly concurrent with the WARN messages, application code may encounter exceptions similar to one or more of the following:
Could not enlist in transaction on entering meta-aware object!
java.lang.IllegalStateException: Transaction TransactionImple < ... status: ActionStatus.ABORTED > is not active STATUS_ROLLEDBACK
- See also Unable to enlist resource ...
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 4
- 5
- 6
- 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.