[JCR-3770] refine validateHierarchy check in order to avoid false-positives

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8, 2.6.6
• Component/s: jackrabbit-core
• Assignee: Stefan Guggisberg
• Reporter: Stefan Guggisberg
• Created: 15/Apr/14 14:28
• Updated: 18/Jun/14 09:53
• Resolved: 15/Apr/14 15:41

Description

if a node is deleted and re-added with the same nodeId (within the same changeLog), validateHierarchy might mistakenly throw an exception, e.g.

Caused by: org.apache.jackrabbit.core.state.ItemStateException: Parent of node with id 37e8c22a-5fa7-4dd8-908e-c94249f3715a has been deleted
at org.apache.jackrabbit.core.state.SharedItemStateManager.validateModified(SharedItemStateManager.java:1352)
at org.apache.jackrabbit.core.state.SharedItemStateManager.validateHierarchy(SharedItemStateManager.java:1199)
...

Issue Links

• relates to: JCR-2598 Saving concurrent sessions executing random operations causes a corrupt JCR