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

Mark Little (JIRA) jira-events at lists.jboss.org
Sun Mar 31 04:22:43 EDT 2013


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

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

This may also relate to https://issues.jboss.org/browse/JBTM-648 in so much as the issue could have been masked by the use of our own locking implementation in the past which was less optimal (e.g., reduced the chance of race conditions.)
                
> 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