[JCR-4121] ConcurrentModificationException in InternalVersionHistoryImpl.fixLegacy()

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4, 1.5, 1.6, 2.0, 2.1, 2.2, 2.4, 2.6, 2.8, 2.10, 2.12.0, 2.14
• Fix Version/s: 2.16, 2.12.7, 2.14.1, 2.10.6, 2.4.8, 2.6.9, 2.8.6, 2.15.2
• Component/s: jackrabbit-core
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 14/Mar/17 10:24
• Updated: 20/Oct/17 12:46
• Resolved: 15/Mar/17 13:01

Description

In some cases the method InternalVersionHistoryImpl.fixLegacy() may trigger a ConcurrentModificationException. The exception is caused by the iterator on the nameCache.keySet(). It only happens when the root version points to a successor version which has a same name sibling. In this case the legacyResolveSuccessors() will trigger a reload(), which in turn calls init() and then clears the nameCache. A version history does not actually allow same name sibling child nodes, but one of the repository instance I have access to does show this kind of structure.

See also related issues JCR-3086 & JCR-1111.

Issue Links

• relates to: JCR-1111 Access to version history results in reading all versions of versionable node