[JCR-3239] Removal of a top level node doesn't update the hierarchy manager's cache.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.2.11, 2.4
• Component/s: jackrabbit-core
• Assignee: Unassigned
• Reporter: Philipp Bärfuss
• Created: 20/Feb/12 16:28
• Updated: 27/Nov/14 22:38

Description

Problem

Scenario in which I encounter the problem:

• given a node 'test' under root (/test)
• re-imported the node after a deletion (all in-session operations)

session.removeItem("/test")
session.getImportXML("/", stream, ImportUUIDBehavior.IMPORT_UUID_COLLISION_THROW)

Result: throws an ItemExistsException

If the same operations are executed deeper in the hierarchy (for instance /foo/bar) then the code works perfectly fine.

Findings

• session.removeItem informs the hierachy manager (via listener)
  --> CachingHierarchyManager.nodeRemoved(NodeState, Name, int, NodeId)
• but the root node (passed as state) is not in the cache and hence the entry of the top level node is not removed
  --> CachingHierarchyManager: 458
• while trying to import the method SessionImporter.startNode(NodeInfo, List<PropInfo>) calls session.getHierarchyManager().getName(id) (line 400)
• the stall information causes a uuid collision (the code expects an exception if the node doesn't exist but in this case it returns the name of the formerly removed node)

Note: session.itemExists() and session.getNode() work as expected (the former returns false, the later throws an ItemNotFound exception)
Note: I know that a different import behavior (replace existing) would solve the issue but I can't be 100% sure that the UUID match so I favor collision throw in my case.

Issue Links

• relates to: JCR-3779 Node.getPath() returns inconsistent values depending on whether node is saved or not