felix-dev mailing list archives

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

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

Thomas Diesler commented on FELIX-4237:
---------------------------------------

Intermittently reproducible by: [ConfiguredReferenceTestCase|https://github.com/tdiesler/jbosgi/blob/master/testsuite/functional/src/test/java/org/jboss/test/osgi/ds/ConfiguredReferenceTestCase.java]
                
> 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
repeated.
> 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

Mime
View raw message