[ 
https://issues.apache.org/jira/browse/FELIX-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498918#comment-13498918
 ] 

Felix Meschberger edited comment on FELIX-3762 at 11/16/12 5:53 PM:
--------------------------------------------------------------------

This is probably what happens:

1 Thread created (not started)
2 ConfigurationAdmin service is registered and a ServiceListener is creating or 
updating configuration
3 An UpdateTask is created which sets the "helper" field in the constructor
4 The managedService[Factory]Trackers are created
5 The threads are started and the UpdateTask executed

The problem is step 3 where the helper field is set as a reference to the 
appropriate managedService[Factory]Tracker. Since this is still null, this 
fails.
                
      was (Author: fmeschbe):
    Right, I cannot explain this. Maybe a log file (DEBUG level) with more 
context would help ?
                  
> 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
>
> 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

Reply via email to