You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2006/05/31 19:10:31 UTC
[jira] Created: (JCR-447) deadlock on concurrent commit/locking
deadlock on concurrent commit/locking
-------------------------------------
Key: JCR-447
URL: http://issues.apache.org/jira/browse/JCR-447
Project: Jackrabbit
Type: Bug
Versions: 1.0, 1.0.1, 0.9
Environment: r410507
Reporter: Tobias Bocanegra
Assigned to: Tobias Bocanegra
there can happen an iterlock between the dispatching part of the shared item state manager and the lockmanager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (JCR-447) deadlock on concurrent commit/locking
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-447?page=all ]
Tobias Bocanegra closed JCR-447:
--------------------------------
Resolution: Fixed
added very ugly hack by disably write lock inside the version specific item state manager during transaction commits.
fixed in revision 410655.
> deadlock on concurrent commit/locking
> -------------------------------------
>
> Key: JCR-447
> URL: http://issues.apache.org/jira/browse/JCR-447
> Project: Jackrabbit
> Type: Bug
> Versions: 0.9, 1.0, 1.0.1
> Environment: r410507
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
>
> there can happen an iterlock between the dispatching part of the shared item state manager and the lockmanager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira