You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2017/03/14 10:24:41 UTC

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

Marcel Reutegger created JCR-4121:
-------------------------------------

             Summary: ConcurrentModificationException in InternalVersionHistoryImpl.fixLegacy()
                 Key: JCR-4121
                 URL: https://issues.apache.org/jira/browse/JCR-4121
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 2.14, 2.12.0, 2.10, 2.8, 2.6, 2.4, 2.2, 2.1, 2.0, 1.6, 1.5, 1.4
            Reporter: Marcel Reutegger
            Assignee: Marcel Reutegger
            Priority: Minor
             Fix For: 2.15.2


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 is missing. In this case the {{legacyResolveSuccessors()}} will trigger a {{reload()}}, which in turn calls {{init()}} and then clears the {{nameCache}}.

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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)