Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C461F18A1B for ; Thu, 4 Feb 2016 08:14:40 +0000 (UTC) Received: (qmail 18225 invoked by uid 500); 4 Feb 2016 08:14:40 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 18133 invoked by uid 500); 4 Feb 2016 08:14:40 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 18024 invoked by uid 99); 4 Feb 2016 08:14:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2016 08:14:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0711E2C1F6D for ; Thu, 4 Feb 2016 08:14:40 +0000 (UTC) Date: Thu, 4 Feb 2016 08:14:40 +0000 (UTC) From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KARAF-3798) FeaturesServiceImpl not threadsafe MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-3798?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofr=C3=A9 updated KARAF-3798: ---------------------------------------- Fix Version/s: 4.0.5 4.1.0 > 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=C3=A9 > Fix For: 4.1.0, 4.0.5 > > > This error happens pretty frequently with M3, when there are multiple fea= tures 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 proble= m delivering configuration event to [org.osgi.service.cm.ConfigurationListe= ner, id=3D30, bundle=3D9/mvn:org.apache.felix/org.apache.felix.scr/1.8.2] > java.lang.NullPointerException > =09at org.apache.felix.scr.impl.config.ConfigurationSupport.configuration= Event(ConfigurationSupport.java:283)[9:org.apache.felix.scr:1.8.2] > =09at org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEven= t.sendEvent(ConfigurationManager.java:2036)[3:org.apache.felix.configadmin:= 1.8.4] > =09at org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEven= t.run(ConfigurationManager.java:2005)[3:org.apache.felix.configadmin:1.8.4] > =09at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[3:= org.apache.felix.configadmin:1.8.4] > =09at 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 in= stallFeature calls to FeatureService mess up the state of the bundles. In m= y case it left a bundle in a corrupt state, which was noticed when the conf= iguration change did not really activate the service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)