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

Mark Little (JIRA) jira-events at lists.jboss.org
Sat Mar 30 15:40:43 EDT 2013


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

Mark Little commented on JBTM-1602:
-----------------------------------

I'm not convinced this change is the right one to make or has been applied consistently to the rest of the class. I'll take a look at the test case you had which reproduced the problem and revert some of the optimisations we've applied over the years to LockManager to reduce contention and which have probably introduced this vulnerability.
                
> 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