Paul Robinson created JBTM-1209: ----------------------------------- Summary: XTS recovery tests failing due to a non-empty TXObjectStore after test complete Key: JBTM-1209 URL: https://issues.jboss.org/browse/JBTM-1209 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-java7/411/console Looking at http://172.17.131.2/job/narayana-java7/411/artifact/XTS/localjunit/crash-... you will see: {code} java.lang.AssertionError at org.junit.Assert.fail(Assert.java:92) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertTrue(Assert.java:54) at com.arjuna.qa.junit.BaseCrashTest.tearDown(BaseCrashTest.java:105) {code} This assertion checks that the TXObjectStore is empty after the test completes. For the three tests that failed in this job, the log was not empty. Looking at the end of http://172.17.131.2/job/narayana-java7/411/artifact/XTS/localjunit/crash-... shows you: {code} 10:36:04,605 INFO [stdout] (Periodic Recovery) rule.debug{trace remove committed state} : removed committed transaction 0:ffffac118303:4e49dd0f:50110ed5:10 10:36:04,605 INFO [stdout] (Periodic Recovery) rule.debug{trace remove committed state} : !!!killing JVM!!! {code} This suggests that the transaction log was removed. However, I'm not sure that the Byteman script checks that the participant record has also been removed. It's possible that the AS is being killed slightly too early, before the participant record is removed. We should check other scripts to see if they wait for both logs to be removed. [JBTM-1208] should help debug this problem if we get it again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira