[ https://issues.jboss.org/browse/JBTM-1260?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1260: -------------------------------- Summary: SimpleIsolatedServers testSimultaneousRecover error 4 (was: SimpleIsolatedServers error 4) -- 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

[ https://issues.jboss.org/browse/JBTM-1260?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1260: ------------------------------------- Similar issue, at the same time as a remote recovery manager is rolling back an orphan subordinate transaction, the local recovery manager can be scanning for orphans as the recover TMSTARTSCAN lock cannot be observed To be clear: 1. Remote recovery manager scans for orphan subordinates, locates one and starts the roll back process 2. Local recovery manager scans XARs for Xids, gets one back 3. Remote recovery manager rolls back the subordinate (and therefore the XAR) 4. Local recovery manager looks at XAR Xid to see if it has a transaction, it doesn't (any more due to step 3 above) so tries to roll it back, causes the test to fail as the XAR::rollback increments the counter Will only increment the counter on successful rollback -- 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

[ https://issues.jboss.org/browse/JBTM-1260?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1260: ------------------------------------- to be clear, the transaction can complete however it likes (commit/rollback), what can happen is that a scan of XAR can return the xid as indoubt and a separate (remote) recovery manager thread complete the transaction then we can't find the transaction so try to roll it back. to the rm it would get either (commit(xid1), rollback(xid1)) or (rollback(xid1), rollback(xid1)). Although its not nice and gets an exception it won't have data integrity implications -- 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

[ https://issues.jboss.org/browse/JBTM-1260?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1260. --------------------------------- Resolution: Done http://172.17.131.2/job/btny-pulls-narayana/121/ https://github.com/jbosstm/narayana/pull/102 -- 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

[ https://issues.jboss.org/browse/JBTM-1260?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1260. ------------------------------- -- 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

[ https://issues.jboss.org/browse/JBTM-1260?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1260: -------------------------------- Component/s: JTA Testing -- 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