[JCR-3115] Versioning fixup leaves persistence in a state where the node can't be made versionable again

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.2.10, 2.3.2
• Component/s: jackrabbit-core, versioning
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 14/Oct/11 13:34
• Updated: 09/Mar/17 21:23
• Resolved: 18/Oct/11 15:11

Description

Jackrabbit's version recovery mode (org.apache.jackrabbit.version.recovery system property) disconnects all version histories that expose problems that manifest in unexpected exceptions being thrown. "disconnects" means removing the properties defined for mix:versionable and removing the mixin type. The actual versioning related nodes remain in place.

The problem: when re-adding mix:versionable, ItemSaveOperation.initVersionHistories tries to create the new version history in the same location (the path being derived from the versionable node's identifier), and consequently fails because of the broken underlying storage.

(attaching a work-in-progress test case that illustrates the problem)

Issue Links

• breaks: JCR-4118 RepositoryChecker creates invalid node names
• relates to: JCR-3181 add test case for recovering from broken version history hierarchy