[FELIX-1195] NullPointerException in ComponentActivatorTask if component is destroyed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: scr-1.0.8
• Fix Version/s: scr-1.2.0
• Component/s: Declarative Services (SCR)
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 02/Jun/09 08:48
• Updated: 31/Jul/09 15:07
• Resolved: 02/Jun/09 08:50

Description

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.