felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Escoffier (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FELIX-3672) Potential Concurrent Modification Exception when a bundle is stopped
Date Thu, 20 Sep 2012 12:50:07 GMT
Clement Escoffier created FELIX-3672:

             Summary: Potential Concurrent Modification Exception when a bundle is stopped
                 Key: FELIX-3672
                 URL: https://issues.apache.org/jira/browse/FELIX-3672
             Project: Felix
          Issue Type: Bug
          Components: iPOJO
    Affects Versions: ipojo-core-1.8.2
            Reporter: Clement Escoffier
            Assignee: Clement Escoffier
             Fix For: ipojo-core-1.8.4

There is a potential CME when a bundle declaring instances is stopped.

The exception we see in the logs is: -
31.07.2012 14:54:10.281 *ERROR* [FelixDispatchQueue] org.apache.felix.ipojo FrameworkEvent
ERROR (java.util.ConcurrentModificationException) java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$KeyIterator.next(HashMap.java:828)
at org.apache.felix.ipojo.InstanceCreator.removeInstancesFromBundle(InstanceCreator.java:117)
at org.apache.felix.ipojo.Extender.closeManagementFor(Extender.java:147)
at org.apache.felix.ipojo.Extender.bundleChanged(Extender.java:129)

The instance deletion is not protected against concurrent access.

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

View raw message