jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-447) deadlock on concurrent commit/locking
Date Wed, 31 May 2006 20:10:30 GMT
     [ 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


Mime
View raw message