[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1611: ---------------------------------------- I have been unable to replicate the issue on my laptop using the command: {noformat} ant -f run-tests.xml -Dtest.name=crashrecovery09 -Dtest.methods="CrashRecovery09_Test01" -Dprofile=hornetq onetest {noformat} and similarly for the other two failing methods in this test group and the other two test groups (crashrecover10 and crashrecover12). Therefore it looks like the issue is environmental. I have just debugged one of the other QA crash recovery issues (JBTM-1601) and there I found that the client wasn't waiting long enough for recovery to kick in. Extending the wait period before checking for success fixed that issue but unfortunately these test groups uses a different method to wait for recovery. In this case the clients trigger a remote recovery scan. The internal interface does allow the client to trigger multiple passes but the first two test groups have the number of scans hardcoded to 1 and the last group does 2 passes so its not configurable. To test the theory we could either: # run the test on a fast machine, or # I patch the QA test suite so that scan counter is configurable and introduce a pause between scans If either of these approaches work we can put the fix into 4.17.5 -- 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