felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-5192) ConfigurationDependency race condition when component is stopped
Date Tue, 01 Mar 2016 23:53:18 GMT

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

Pierre De Rop updated FELIX-5192:
    Fix Version/s:     (was: 	org.apache.felix.dependencymanager-r7)

> ConfigurationDependency race condition when component is stopped
> ----------------------------------------------------------------
>                 Key: FELIX-5192
>                 URL: https://issues.apache.org/jira/browse/FELIX-5192
>             Project: Felix
>          Issue Type: Bug
>          Components: Dependency Manager
>    Affects Versions: org.apache.felix.dependencymanager-r1
>            Reporter: Pierre De Rop
>            Assignee: Pierre De Rop
>             Fix For: org.apache.felix.dependencymanager-r8
> When a component is being removed (stopped) and at the same time a configuration is updated
or removed, then it may be possible that
> the configuration dependency invokes the updated callback after the component instance
has been destroyed and nullified.
> So far, this was never observed because we did not log any warnings when a configuration
callback was unavailable, but now we log a warn (see  FELIX-5187).
> The fix to do is simply to check if the configuration dependency is started before invoking
the update callback method.

This message was sent by Atlassian JIRA

View raw message