[ https://issues.jboss.org/browse/WFLY-5319?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-5319: ------------------------------------ Just challenging myself and my assertion in the negativeTxTimeoutVerifyReaperThreadCanceledTxTest method. Current code is: {code} /** * Repeat the same test as test_negativeTxTimeoutTest but also ensure that the reaper thread canceled the tx. * If this test fails, it could be that the tx reaper thread name changed or we are using a different tx manager. * * @throws Exception */ // @Ignore // WFLY-5319 is for fixing this test (see failure https://gist.github.com/scottmarlow/6409290362f35f2d1320) @Test @InSequence(3) public void test_negativeTxTimeoutVerifyReaperThreadCanceledTxTest() throws Exception { TestEntityManager.clearState(); assertFalse("entity manager state is not reset", TestEntityManager.getClosedByReaperThread()); SFSB1 sfsb1 = lookup("ejbjar/SFSB1", SFSB1.class); try { sfsb1.createEmployeeWaitForTxTimeout(true, "Wily", "1 Appletree Lane", 10); } catch (Exception e) { // ignore the tx rolled back exception // } assertFalse("entity manager should not of been closed by the reaper thread", TestEntityManager.getClosedByReaperThread()); assertTrue("transaction was canceled by reaper thread", SFSB1.isAfterCompletionCalledByTMTimeoutThread()); } {code} We are failing the second assertion "assertTrue("transaction was canceled by reaper thread", SFSB1.isAfterCompletionCalledByTMTimeoutThread())". I am trying to get more information out of this test case by recording the thread name of which the afterCompletion was called from (should be the reaper thread or application thread. Once we have the thread name from the failing case, we can determine next steps to update the test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)