[ https://issues.jboss.org/browse/JBTM-2080?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2080. ------------------------------------ Resolution: Cannot Reproduce Bug The failure is spurious: - I set up dedicated jobs (with extra debug) to run 500 iterations (on CI, job JBTM-2080) and 1512 iterations on my laptop with no failures. I'll leave the CI for now just in case we get lucky and it happens again. The test starts 2 servers, the second one configured with CrashBehaviorCrashInRollback. In part two the server looks up the recovery coordinator IOR for the resource that failed and triggers a replay_completion attempt (it connected with the rcv coord at 08:06:58,945, the rcv coord gets the replay request at 08:06:59,004 and finishes processing the request at 08:06:59,006 returning StatusUnknown. There is no narayana logging corresponding to why it cannot determine the status. The unknown status can occur for a various reasons and there just isn't the evidence to point to any cause as being more likely than any other but the most obvious culprit is a spurious comms failure (in these tests the recovery manager runs out of process). I configured the jobs with trace logging so as to determine the precise reason for replay_completion StatusUnknown so it's a shame we couldn't trigger the problem. -- 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