jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Quellenberg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3471) ConcurrentModificationException in InternalVersionHistoryImpl.fixLegacy
Date Fri, 14 Dec 2012 12:24:14 GMT

     [ https://issues.apache.org/jira/browse/JCR-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom Quellenberg updated JCR-3471:
---------------------------------

    Attachment: JCR-3471.patch

Please find attached a simple fix for the problem.

The problem is triggered by a corrupted version history. The root version contains a non existing
successor. This is handled by InternalVersionImpl.getSuccessors() (s. JCR-2655). In this function
a call to versionHistory.getVersion(..) for a non existing node is done. The getVersion(..)
triggers a InternalVersionHistoryImpl.reload() which leads to a modified nameCache and in
the end to a ConcurrentModificationException.


                
> ConcurrentModificationException in InternalVersionHistoryImpl.fixLegacy
> -----------------------------------------------------------------------
>
>                 Key: JCR-3471
>                 URL: https://issues.apache.org/jira/browse/JCR-3471
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.4.3
>            Reporter: Tom Quellenberg
>            Priority: Minor
>         Attachments: JCR-3471.patch
>
>
> {code}
> java.util.ConcurrentModificationException: null
>         at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:373)
~[na:1.6.0_16]
>         at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:384) ~[na:1.6.0_16]
>         at org.apache.jackrabbit.core.version.InternalVersionHistoryImpl.fixLegacy(InternalVersionHistoryImpl.java:170)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.version.InternalVersionHistoryImpl.<init>(InternalVersionHistoryImpl.java:114)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.version.InternalVersionManagerBase.createInternalVersionItem(InternalVersionManagerBase.java:865)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.version.InternalVersionManagerImpl.getItem(InternalVersionManagerImpl.java:335)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.version.InternalXAVersionManager.getItem(InternalXAVersionManager.java:432)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.version.InternalVersionManagerBase.getVersionHistory(InternalVersionManagerBase.java:138)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.version.InternalXAVersionManager.getVersionHistory(InternalXAVersionManager.java:56)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.version.VersionManagerImplBase.getVersionHistory(VersionManagerImplBase.java:357)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.VersionManagerImpl.access$700(VersionManagerImpl.java:73)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.VersionManagerImpl$4.perform(VersionManagerImpl.java:184)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.VersionManagerImpl$4.perform(VersionManagerImpl.java:180)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.VersionManagerImpl.perform(VersionManagerImpl.java:96)
~[jackrabbit-core-2.4.3.jar:2.4.3]
>         at org.apache.jackrabbit.core.VersionManagerImpl.getVersionHistory(VersionManagerImpl.java:180)
~[jackrabbit-core-2.4.3.jar:2.4.3]
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message