felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4237) Updating a configuration may deactivate/active component multiple times
Date Tue, 24 Sep 2013 07:43:02 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776084#comment-13776084

David Jencks commented on FELIX-4237:

(1) please verify this is still a problem using DS trunk
(2) can you determine from the log why ServiceD1 is deactivated a second time?  Attaching
a log might be useful.

Are you contributing a test case?  If so please attach it and indicate with the appropriate
check mark that you are licensing it to the asf.  Otherwise I don't think I can look at your
test case.  Does it do anything beyond your description?

david jencks

> Updating a configuration may deactivate/active component multiple times
> -----------------------------------------------------------------------
>                 Key: FELIX-4237
>                 URL: https://issues.apache.org/jira/browse/FELIX-4237
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.6.2
>            Reporter: Thomas Diesler
> * ServiceD has a mandatory unary reference to ServiceD1
> * ServiceD1 is backed by a configuration in ConfigurationAdmin (1.6.0)
> * Activate the services with no configuration
> * Create and update the configuration for ServiceD1
> The observed behaviour is
> * ServiceD gets deactivated
> * ServiceD1 gets deactivated
> * New instance of ServiceD1 is constructed and activated with the configuration
> * ServiceD1 is bound to to a new instance of ServiceD and ServiceD gets activated
> following this ServiceD1 may get deactivated again causing the above sequence to get
> In a large dependency graph this would deactivate/activate all components in the graph.
Component activation may not be cheap and should not be done repeatedly with the same configuration
passed in.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message