You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2007/10/24 14:54:51 UTC
[jira] Resolved: (JCR-1108) JCR2SPI: error level logging when
cleaning up session locks
[ 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.