You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/11/18 19:22:57 UTC

[jira] [Work stopped] (FELIX-3762) NPE in UpdateConfiguration#run

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

Work on FELIX-3762 stopped by Felix Meschberger.

> NPE in UpdateConfiguration#run
> ------------------------------
>
>                 Key: FELIX-3762
>                 URL: https://issues.apache.org/jira/browse/FELIX-3762
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions: configadmin-1.6.0
>            Reporter: Carsten Ziegeler
>            Assignee: Felix Meschberger
>         Attachments: FELIX-3762.patch
>
>
> During startup I sometimes see a set of these NPE's :
> 16.11.2012 04:48:47.004 *ERROR* [CM Configuration Updater (Update: pid=org.apache.sling.servlets.resolver.SlingServletResolver)] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,48] Unexpected problem executing task (java.lang.NullPointerException) java.lang.NullPointerException
> 	at org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1701)
> 	at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)
> 	at java.lang.Thread.run(Thread.java:662)
> 16.11.2012 04:48:47.005 *INFO* [FelixStartLevel] org.apache.felix.configadmin BundleEvent STARTED
> Looking at the code, it seems the configuration update thread is started before managedServiceTracker or managedServiceFactoryTracker are set in the start() method of the ConfigurationManager

--
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