[
https://issues.apache.org/jira/browse/FELIX-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-1195.
------------------------------------
Resolution: Fixed
Added a check for the component state before checking the bundle state in Rev.
780967 and logging the situation separately
> NullPointerException in ComponentActivatorTask if component is destroyed
> ------------------------------------------------------------------------
>
> Key: FELIX-1195
> URL: https://issues.apache.org/jira/browse/FELIX-1195
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.0.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.0.10
>
>
> When a ComponentActivatorTask is about to be run, it checks whether the
> component declaring bundle is active or not. If the component has already
> been destroyed, getting the bundle from the component throws a
> NullPointerException. Though, this exception is caught, it is nasty and the
> logged message does not reflect the actual cause for the problem.
> The ComponentActivatorTask.run method must therefore first check whether the
> component as already been destroyed before checking for the bundle state. If
> the component has already been destroyed, the task cannot run anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
