this is a bug in Jackrabbit implementation and here is the jira issue that is logged against this https://issues.apache.org/jira/browse/JCR-1634
Add in your vote as this would help in getting it resolved quicker. -- View this message in context: http://www.nabble.com/Unlocking%3A-Node-not-locked-by-this-session-tp17448831p17797342.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
