You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Pierre De Rop (JIRA)" <ji...@apache.org> on 2016/02/20 22:04:18 UTC
[jira] [Created] (FELIX-5192) ConfigurationDependency race
condition when component is stopped
Pierre De Rop created FELIX-5192:
------------------------------------
Summary: 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-r7
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
(v6.3.4#6332)