[
https://issues.apache.org/jira/browse/SLING-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176899#comment-14176899
]
Rupert Westenthaler commented on SLING-4077:
--------------------------------------------
I updated the version in Stanbol with http://svn.apache.org/r1633151 (trunk)
and http://svn.apache.org/r1633152 (0.12.1-SNAPSHOT). The local runs of the
integration tests went fine for both versions. However this happens only very
rarely so it is really hard to tell if the issue is really gone.
Based on the code the OsgiInstallerImpl#computeTasks(..) iterates over the keys
of the PersistentResourceList#data map. As the OsgiInstallerImpl#run(..) does
not have any lock while calling OsgiInstallerImpl#computeTasks(..) I assume
that even with the most current release there is still the possibility of an
concurrent modification.
> ConcurrentModificationException in
> o.a.sling.installer.core.impl.OsgiInstallerImpl
> ----------------------------------------------------------------------------------
>
> Key: SLING-4077
> URL: https://issues.apache.org/jira/browse/SLING-4077
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.5.0, Installer Core 3.5.4
> Environment: Apache Sling Launcher as used by Apache Stanbol trunk
> versin using Installer Core 3.5.0.
> Reporter: Rupert Westenthaler
>
> When starting the Apache Stanbol Launchers I do see sometimes CME such as.
> {code}
> 16.10.2014 13:58:41.832 *ERROR* [OsgiInstallerImpl]
> org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception
> in Thread Thread[OsgiInstallerImpl,5,main]
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
> at java.util.HashMap$KeyIterator.next(HashMap.java:928)
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.computeTasks(OsgiInstallerImpl.java:586)
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:242)
> at java.lang.Thread.run(Thread.java:724)
> {code}
> Looks like as if iterations over the PersistentResourceList need to get
> synchronized.
> The above exception is reported against version 3.5.0 however as the affected
> code as not changed in 3.5.4 I expect this version to also be affected by
> this. Because of that I also added this version to the list of affected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)