Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <3915882.1163161717126.JavaMail.jira@brutus>
Date: Fri, 10 Nov 2006 04:28:37 -0800 (PST)
From: "Przemo Pakulski (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Created: (JCR-632) VersionManager lock not released in some
 circumstances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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