[JCR-1875] Failing Node.unlock() might leave inconsistent transient state

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6
• Component/s: jackrabbit-core, locks
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 21/Nov/08 16:08
• Updated: 13/Aug/09 15:03
• Resolved: 08/Jan/09 11:58

Description

Similar to issue JCR-538 but for Node.unlock():

If updating the lock related properties (jcr:lockIsDeep or jcr:lockOwner) fails e.g. due to missing permission, there might be inconsistent transient modifications pending.