[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184995#comment-13184995 ]
Julian Reschke commented on JCR-2859: ------------------------------------- The problem is caused by LockInfoImpl in SPI assuming that seeing the lock token implies owning the Lock. > Make open scoped locks recoverable > ---------------------------------- > > Key: JCR-2859 > URL: https://issues.apache.org/jira/browse/JCR-2859 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: locks > Reporter: Carsten Ziegeler > Assignee: Julian Reschke > Fix For: 2.5 > > Attachments: JCR-2859.diff, JCR-2859.patch, OpenScopeLockTest.java > > > The lock tokens for open scoped locks are currently tied to the session which > created the lock. If the session dies (for whatever reason) there is no way > to recover the lock and unlock the node. > There is a theoretical way of adding the lock token to another session, but > in most cases the lock token is not available. > Fortunately, the spec allows to relax this behaviour and I think it would > make sense to allow all sessions from the same user to unlock the node - this > is still in compliance with the spec but would make unlocked locked nodes > possible in a programmatic way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira