jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-194) dead lock while locking or unlocking nodes
Date Tue, 23 Aug 2005 14:12:09 GMT
     [ http://issues.apache.org/jira/browse/JCR-194?page=all ]
     
Dominique Pfister resolved JCR-194:
-----------------------------------

    Fix Version: 1.0
     Resolution: Fixed

Another concurrency issue: whereas deadlock has now been removed, two competing threads, locking
and unlocking at about the same time could invalidate each other's node representation. Thanks
again to Walter Raboch for finding this issue.

Fixed in r239410.

> dead lock while locking or unlocking nodes
> ------------------------------------------
>
>          Key: JCR-194
>          URL: http://issues.apache.org/jira/browse/JCR-194
>      Project: Jackrabbit
>         Type: Bug
>   Components: locks
>     Versions: 1.0
>  Environment: Win XP, Sun JDK 1.5.0
>     Reporter: Walter Raboch
>     Assignee: Dominique Pfister
>      Fix For: 1.0
>  Attachments: SharedItemStateManager.diff
>
> JackRabbit is still hanging on the Node.lock() or Node.unlock() function.
> ... everything fine until here...
> s13: 4
> s13: 5
> s13: 6
> s13: 7   -> unlock()
> s14: started.
> s14: 1   -> session.getRootNode()
> s15: started.
> s15: 1
> s16: started.
> I just find this failure during the first run (emtpy repository home directory). 2nd
and 3th run are fine after killing the vm from first run, but with already initialized repository
directory these time.
> 1. rm -rf repository.home
> 2. run -> hang
> 3. kill
> 4. run -> ok
> 5. run -> ok

-- 
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