You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Claus Köll (JIRA)" <ji...@apache.org> on 2012/06/22 10:39:43 UTC
[jira] [Created] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Claus Köll created JCR-3354:
-------------------------------
Summary: 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
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
[jira] [Updated] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Posted by "Alex Parvulescu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu updated JCR-3354:
---------------------------------
Fix Version/s: 2.5.1
> 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
[jira] [Updated] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Posted by "Claus Köll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Köll updated JCR-3354:
----------------------------
Status: Patch Available (was: Open)
> 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
>
> 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
[jira] [Commented] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Posted by "Unico Hommes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464571#comment-13464571 ]
Unico Hommes commented on JCR-3354:
-----------------------------------
Backported to the 2.2 branch in revision 1390907.
> 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.2.13, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Posted by "Unico Hommes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Unico Hommes updated JCR-3354:
------------------------------
Fix Version/s: 2.2.13
> 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.2.13, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Posted by "Claus Köll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Köll updated JCR-3354:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed in revision 1354499.
> 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
>
> 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
[jira] [Updated] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Posted by "Claus Köll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Köll updated JCR-3354:
----------------------------
Attachment: JCR-3354.patch
I have extended the ReentrantWriterPreferenceReadWriteLock but maybe we should use default Java Locking Mechanism because in JCR-2089 we wanted to remove the dependency to EDU.oswego.cs.dl.util.concurrent
> 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
>
> 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
[jira] [Commented] (JCR-3354) The ReadWriteLock in AbstractJournal
can create a Deadlock in XA Environment
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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