[ https://issues.jboss.org/browse/WFLY-1346?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-1346: ------------------------------- Attachment: server.zip In server.log, see: {quote} Caused by: javax.transaction.RollbackException: JBAS014585: Transaction 'TransactionImple < ac, BasicAction: 0:ffff7f000001:-2b244d5f:519d6b0e:1f81 status: ActionStatus.ABORTED >' was already rolled back {quote} which is the expected (new) message when the reaper thread times out the tx. In the next unit test, the same "pool-1-thread-4" thread is used and the same (cancelled) transaction is still present (causing test subsequent failures). The following is logged in CMTTxInterceptor.required() if a transaction is found and its not active: {quote} 21:10:24,808 ERROR [org.jboss.as.ejb3] (pool-1-thread-4) java.lang.Exception: tx is not active TransactionImple < ac, BasicAction: 0:ffff7f000001:-2b244d5f:519d6b0e:1f81 status: ActionStatus.ABORTED > {quote} Then the same (next) test fails with: {quote} 21:10:24,809 ERROR [org.jboss.as.ejb3.invocation] (pool-1-thread-4) JBAS014134: EJB Invocation failed on component SFSBTopLevel for method public void org.jboss.as.test.integration.jpa.sibling.SFSBTopLevel.createEmployee(java.lang.String,java.lang.String,int): javax.ejb.EJBTransactionRolledbackException: No transaction is running {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira