[jbossts-issues] [JBoss JIRA] (JBTM-1260) atsintegration SimpleIsolatedServers testSimultaneousRecover error 4

[Tom Jenkinson (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720044#comment-12720044 ] 

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

                
> atsintegration SimpleIsolatedServers testSimultaneousRecover error 4
> --------------------------------------------------------------------
>
>                 Key: JBTM-1260
>                 URL: https://issues.jboss.org/browse/JBTM-1260
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>             Fix For: 5.0.0.M2
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-java6/1356/
> Running com.arjuna.ats.jta.distributed.SimpleIsolatedServers
> Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 34.634 sec <<< FAILURE!
> Results :
> Failed tests:   testSimultaneousRecover(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): 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