jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Przemo Pakulski (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-632) VersionManager lock not released in some circumstances
Date Fri, 10 Nov 2006 12:32:41 GMT
     [ http://issues.apache.org/jira/browse/JCR-632?page=all ]

Przemo Pakulski updated JCR-632:
--------------------------------

    Attachment: JCR-632

Attached simple patch solving this issue.

> VersionManager lock not released in some circumstances
> ------------------------------------------------------
>
>                 Key: JCR-632
>                 URL: http://issues.apache.org/jira/browse/JCR-632
>             Project: Jackrabbit
>          Issue Type: Bug
>            Reporter: Przemo Pakulski
>            Priority: Critical
>         Attachments: JCR-632
>
>
> In some circumstances it is possible that lock is not released in VersionManager.checkin
method.
> There is following block of code in checkin nethod :
>         aquireReadLock();
>         try {
>               .....
>         } catch (IllegalStateException e) {
>             releaseReadLock();
>             throw new RepositoryException("Unable to start edit operation.");
>         }
> Lock release should be in finally block to make sure that lock is released when unexpected
exception is thrown.
> In our environment we are getting NPE in mentioned block of code, it results in persisten
lock. 
> No versioning operation is possible and our application server is running ot of threads
(all threads are locked).

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