Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <7734683.1164309663909.JavaMail.jira@brutus>
Date: Thu, 23 Nov 2006 11:21:03 -0800 (PST)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-632) VersionManager lock not released in some
 circumstances
In-Reply-To: <3915882.1163161717126.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-632?page=all ]

Jukka Zitting resolved JCR-632.
-------------------------------

    Fix Version/s: 1.2
                       (was: 1.1.1)
       Resolution: Fixed

Resolved in revision 478645 as a side effect of the JCR-546 fix.

As discussed in JCR-546, this change will not yet be included in the 1.1.1 release.

> VersionManager lock not released in some circumstances
> ------------------------------------------------------
>
>                 Key: JCR-632
>                 URL: http://issues.apache.org/jira/browse/JCR-632
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: versioning
>    Affects Versions: 1.0, 1.0.1, 1.1, 0.9
>            Reporter: Przemo Pakulski
>         Assigned To: Jukka Zitting
>            Priority: Critical
>             Fix For: 1.2
>
>         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