WARN during rollback of TX
markus78 Feb 29, 2012 10:13 AMI have a usertransaction that timesout and should be rolled back, and when that happends I get the following in the logs
14:47:35,745 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff82ef5b2b:7087257b:4f4debce:4cd5f in state RUN 14:47:35,748 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffff82ef5b2b:7087257b:4f4debce:4cd5f invoked while multiple threads active within it. 14:47:35,749 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffff82ef5b2b:7087257b:4f4debce:4cd5f aborting with 1 threads active! 14:47:36,248 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff82ef5b2b:7087257b:4f4debce:4cd5f in state CANCEL 14:47:36,751 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff82ef5b2b:7087257b:4f4debce:4cd5f in state CANCEL_INTERRUPTED 14:47:36,752 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012120: TransactionReaper::check worker Thread[Transaction Reaper Worker 0,5,main] not responding to interrupt when cancelling TX 0:ffff82ef5b2b:7087257b:4f4debce:4cd5f -- worker marked as zombie and TX scheduled for mark-as-rollback 14:47:36,753 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012110: TransactionReaper::check successfuly marked TX 0:ffff82ef5b2b:7087257b:4f4debce:4cd5f as rollback only 14:50:31,481 WARN [com.arjuna.ats.jta] (Transaction Reaper Worker 0) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff82ef5b2b:7087257b:4f4debce:4cd5f, node_name=1, branch_uid=0:ffff82ef5b2b:7087257b:4f4debce:4cdff, subordinatenodename=null, eis_name=unknown eis name > (org.jboss.ejb.client.EJBClientManagedTransactionContext$ResourceImpl@162172c) failed with exception code -: java.lang.IllegalStateException: No EJB client context is available at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:233) at org.jboss.ejb.client.EJBClientManagedTransactionContext$ResourceImpl.rollback(EJBClientManagedTransactionContext.java:234) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:345) [jbossjts-4.16.2.Final.jar:] at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2874) [jbossjts-4.16.2.Final.jar:] at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2853) [jbossjts-4.16.2.Final.jar:] at com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1616) [jbossjts-4.16.2.Final.jar:] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:118) [jbossjts-4.16.2.Final.jar:] at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:217) [jbossjts-4.16.2.Final.jar:] at com.arjuna.ats.arjuna.coordinator.TransactionReaper.doCancellations(TransactionReaper.java:370) [jbossjts-4.16.2.Final.jar:] at com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:78) [jbossjts-4.16.2.Final.jar:]
Should I worry about this? later in the logs it seems the TX is "killed off" ... Not sure why I get the "No EJB Client context" warning, ideas anyone?