Example Hibernate and Transactions subsystem interaction when Transaction Reaper ABORTS a Transaction in JBoss
Issue
WARN
,INFO
logging similar to (note theERROR
log entry will be database specific):
WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX <tx-id> in state RUN
WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id <tx-id> invoked while multiple threads active within it.
WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action <tx-id> aborting with 1 threads active!
WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB default - 4) SQL Error: 1013, SQLState: 72000
ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB default - 4) ORA-01013: user requested cancel of current operation
INFO [org.hibernate.engine.jdbc.internal.LogicalConnectionImpl] (EJB default - 4) HHH000106: Forcing container resource cleanup on transaction completion
WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX <tx-id>
Environment
- Red Hat JBoss Enterprise Application Platform 6
default-timeout
defined injboss-as-txn_1_0.xsd
jboss-as-txn_1_1.xsd
jboss-as-txn_1_2.xsd
- Errors in progression
ARJUNA012117
ARJUNA012095
ARJUNA012108
HHH000106
ARJUNA012121
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.