Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <27450881.1193230491098.JavaMail.jira@brutus>
Date: Wed, 24 Oct 2007 05:54:51 -0700 (PDT)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-1108) JCR2SPI: error level logging when
 cleaning up session locks
In-Reply-To: <3102112.1188833698857.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-1108.
-------------------------

       Resolution: Fixed
    Fix Version/s: 1.4

> JCR2SPI: error level logging when cleaning up session locks 
> ------------------------------------------------------------
>
>                 Key: JCR-1108
>                 URL: https://issues.apache.org/jira/browse/JCR-1108
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: SPI
>            Reporter: Julian Reschke
>            Assignee: angela
>            Priority: Minor
>             Fix For: 1.4
>
>
> LockManagerImpl.loggingOut() tries to unlock nodes that have a session lock. If, while doing so, a RepositoryException is thrown, this gets locked on error level.
> The TCK tests tearDown code removes test nodes using a separate session; thus we see RepositoryExceptions for the simple reason that the nodes have already been removed by somebody else.
> Proposal: handle ItemNotFoundExc and PathNotFoundExc separately, not logging them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.