jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3354) The ReadWriteLock in AbstractJournal can create a Deadlock in XA Environment
Date Fri, 03 Aug 2012 10:17:04 GMT

    [ https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427959#comment-13427959
] 

Jukka Zitting commented on JCR-3354:
------------------------------------

Merged to the 2.4 branch in revision 1368865.
                
> The ReadWriteLock in AbstractJournal can create a Deadlock in XA Environment
> ----------------------------------------------------------------------------
>
>                 Key: JCR-3354
>                 URL: https://issues.apache.org/jira/browse/JCR-3354
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.4.2
>            Reporter: Claus Köll
>            Assignee: Claus Köll
>             Fix For: 2.4.3, 2.5.1
>
>         Attachments: JCR-3354.patch
>
>
> The writeLock will be created on prepare() and will be released on commit().
> If different threads will be used a the writeLock could not be released.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message