[ https://issues.apache.org/jira/browse/KARAF-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380661#comment-15380661 ]
Alexey Markevich commented on KARAF-3798: ----------------------------------------- even after this fix a parallel call (3 in my case) to {code} featuresService.installFeature(feature, FEATURE_OPTIONS); {code} and after {code} featuresService.uninstallFeature(id, version, FEATURE_OPTIONS); {code} cause "Feature named 'id/version' is not installed" > FeaturesServiceImpl not threadsafe > ---------------------------------- > > Key: KARAF-3798 > URL: https://issues.apache.org/jira/browse/KARAF-3798 > Project: Karaf > Issue Type: Bug > Components: karaf-feature > Affects Versions: 4.0.0.M3 > Reporter: Fabian Lange > Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6 > > Attachments: Screen Shot 2016-06-24 at 12.57.40.png > > > This error happens pretty frequently with M3, when there are multiple > features installed on startup and config files to activate them created. > {code} > 2015-06-19 15:55:12,249 | ERROR | 43-3aaf88a7bd8b) | configadmin > | 3 - org.apache.felix.configadmin - 1.8.4 | Unexpected problem > delivering configuration event to [org.osgi.service.cm.ConfigurationListener, > id=30, bundle=9/mvn:org.apache.felix/org.apache.felix.scr/1.8.2] > java.lang.NullPointerException > at > org.apache.felix.scr.impl.config.ConfigurationSupport.configurationEvent(ConfigurationSupport.java:283)[9:org.apache.felix.scr:1.8.2] > at > org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2036)[3:org.apache.felix.configadmin:1.8.4] > at > org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2005)[3:org.apache.felix.configadmin:1.8.4] > at > org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[3:org.apache.felix.configadmin:1.8.4] > at java.lang.Thread.run(Thread.java:745)[:1.8.0_40] > {code} > As written in latest comment, the root cause seems to be that multiple > installFeature calls to FeatureService mess up the state of the bundles. In > my case it left a bundle in a corrupt state, which was noticed when the > configuration change did not really activate the service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)