[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-746) Updating a configuration may deactivate/active component multiple times

[Thomas Diesler (JIRA)]

     [ https://issues.jboss.org/browse/JBOSGI-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBOSGI-746.
-----------------------------------

    Resolution: Done


Getting the service before we close the tracker in FrameworkUtils seems to resolve this
                
> Updating a configuration may deactivate/active component multiple times
> -----------------------------------------------------------------------
>
>                 Key: JBOSGI-746
>                 URL: https://issues.jboss.org/browse/JBOSGI-746
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>            Assignee: 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