You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/09/06 10:48:31 UTC
[jira] Created: (FELIX-357) activation and deactivation may run
concurrently
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
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-357) activation and deactivation may run
concurrently
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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 execution.
> 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.
[jira] Closed: (FELIX-357) activation and deactivation may run
concurrently
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-357.
-----------------------------------
Deployed new snapshot 20070906.090557-3 containing the fix.
> 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 execution.
> 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.
[jira] Updated: (FELIX-357) activation and deactivation may run
concurrently
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-357:
------------------------------------
Fix Version/s: scr-1.0.0
> 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 (SCR)
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.0.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (FELIX-357) activation and deactivation may
run concurrently
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-357 started by Felix Meschberger.
> 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 execution.
> 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.
[jira] Assigned: (FELIX-357) activation and deactivation may run
concurrently
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned FELIX-357:
---------------------------------------
Assignee: Felix Meschberger
> 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 execution.
> 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.