felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-357) activation and deactivation may run concurrently
Date Thu, 06 Sep 2007 09:06:31 GMT

     [ https://issues.apache.org/jira/browse/FELIX-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Felix Meschberger resolved FELIX-357.

    Resolution: Fixed

To fix this issue, I have to synchronize these methods such that only one can be executed
at the same time for a given component instance.

Fixed in Rev. 573189.

> activation and deactivation may run concurrently
> ------------------------------------------------
>                 Key: FELIX-357
>                 URL: https://issues.apache.org/jira/browse/FELIX-357
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
> 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
> The current measures in these methods to selectively set the state do not seem to be
adequate to prevent concurrent execution.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message