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-279) Concurrency Issues when enabling components
Date Tue, 15 May 2007 10:42:16 GMT

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

Felix Meschberger resolved FELIX-279.
-------------------------------------

    Resolution: Fixed

Fixed the concurrency issues by having a single actor thread, which is fed with tasks (Runnable).
Whenever a component needs to change state
(enable, activate, deactivate, disable), the respective action is packed in a Runnable and
scheduled for asynchronous operation.

The only exceptions to this rule is the creation of the ComponentManager instance and the
disposal of a ComponentManager. The latter is synchronous to be sure to have the ComponentManager
destroyed before the framework itself takes actions such as unregistering services and taking
class loaders out of service.

Fixed in Rev 538123.

> Concurrency Issues when enabling components
> -------------------------------------------
>
>                 Key: FELIX-279
>                 URL: https://issues.apache.org/jira/browse/FELIX-279
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>         Assigned To: Felix Meschberger
>             Fix For: 1.0.0
>
>
> When bundles are started and their components registered, enabled and activated and configuration
is provided to them, timing issues may occurr, such that in the end some components may not
be started at all.

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


Mime
View raw message