AbstractComponentManager.getBundle() may throw NullPointerException
-------------------------------------------------------------------
Key: FELIX-2091
URL: https://issues.apache.org/jira/browse/FELIX-2091
Project: Felix
Issue Type: Bug
Components: Declarative Services (SCR)
Affects Versions: scr-1.4.0
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: scr-1.4.2
The AbstractComponentManager.getBundle() method may throw NullPointerException
if called after the component has been disposed off. This may cause nasty log
messages in the ComponentActorThread:
12.02.2010 19:08:56.913 *ERROR* [SCR Component Actor] org.apache.felix.scr
Unexpected problem executing task Activate Component:
org.apache.sling.engine.impl.SlingMainServlet (17)
(java.lang.NullPointerException) java.lang.NullPointerException
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.getBundle(AbstractComponentManager.java:201)
at
org.apache.felix.scr.impl.ComponentActivatorTask.run(ComponentActivatorTask.java:60)
at
org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:96)
at java.lang.Thread.run(Unknown Source)
The check whether a component activation task should be executed should include
the possibility that the component has been disposed off and the bundle is null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
