[
https://issues.apache.org/jira/browse/FELIX-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554549
]
Carsten Ziegeler commented on FELIX-443:
----------------------------------------
I applied a fix in revision 607019: instead of directly accessing the
ConfigurationManager from the embedded classes, the CM is passed as an instance
variable and the classes are now static.
> NullPointerException during Startup
> -----------------------------------
>
> Key: FELIX-443
> URL: https://issues.apache.org/jira/browse/FELIX-443
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Reporter: Carsten Ziegeler
>
> I get an NPE with latest code from svn; this happens will trying to process
> the LogbackManager from Sling
> java.lang.NullPointerException
> at
> org.apache.felix.cm.impl.ConfigurationManager.access$400(ConfigurationManager.java:92)
> at
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceTracker.addingService(ConfigurationManager.java:1333)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1021)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.trackInitialServices(ServiceTracker.java:882)
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:289)
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:228)
> at
> org.apache.felix.cm.impl.ConfigurationManager$AbstractManagedServiceTracker.<init>(ConfigurationManager.java:1297)
> at
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceTracker.<init>(ConfigurationManager.java:1322)
> at
> org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:213)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589)
> at org.apache.felix.framework.Felix._startBundle(Felix.java:1583)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1517)
> at
> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1102)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
> at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.