[jbossts-issues] [JBoss JIRA] (JBTM-1602) Determine why 4 locks acquired in LockManager.propagate

Michael Musgrove (JIRA) jira-events at lists.jboss.org
Sun Mar 31 11:57:41 EDT 2013


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

Michael Musgrove commented on JBTM-1602:
----------------------------------------

The test that originally showed up the race condition (org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote#JTSRemote_DistributedHammerTest2) used to fail on average after about 20 runs so 1000 runs with your changes certainly looks to have fixed the original issue. Thanks for fixing this. 
                
> Determine why 4 locks acquired in LockManager.propagate
> -------------------------------------------------------
>
>                 Key: JBTM-1602
>                 URL: https://issues.jboss.org/browse/JBTM-1602
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Core
>    Affects Versions: 5.0.0.M2
>            Reporter: Mark Little
>            Assignee: Mark Little
>


--
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


More information about the jbossts-issues mailing list