[FELIX-357] activation and deactivation may run concurrently

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: scr-1.0.0
• Component/s: Declarative Services (SCR)
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 06/Sep/07 08:47
• Updated: 30/May/08 18:15
• Resolved: 06/Sep/07 09:04

Description

In some situations like multiple static service references actively changing state the AbstractComponentManager.activateInternal and AbstractComponentManager.deactivateInternal may run concurrently due to the fixes introduced by FELIX-341 where the deactivateInternal method is now immediately called but the activateInternal method is still scheduled for asynchronous execution.

The current measures in these methods to selectively set the state do not seem to be adequate to prevent concurrent execution.