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

Mark Little (JIRA) jira-events at lists.jboss.org
Fri Mar 29 17:54:41 EDT 2013

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

Mark Little commented on JBTM-1602:

I just noticed this change in the code and tracked it back to github (no JIRA associated with it, so I couldn't see what the issue was):

               Object syncObject = ((BasicAction.Current() == null) ? getMutex() : BasicAction.Current());

               synchronized (this) {
               synchronized (getMutex()) {
               synchronized (syncObject)

I'm not sure why this change is in here, but need to check because it doesn't look right. Ignoring the fact that we now have 3 locks being acquired before the actual locksHeld lock, we're also potentially acquiring the same lock twice (syncObject could be getMutex())!
> Determine why 4 locks acquired in 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