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/04/26 23:10:13 UTC
[jira] [Resolved] (FELIX-5242) Configuration updates may be missed
when the component is restarting
[ https://issues.apache.org/jira/browse/FELIX-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre De Rop resolved FELIX-5242.
----------------------------------
Resolution: Fixed
Committed a patch in rv 1741103.
To avoid the race conditions, the updated method is scheduled in the component executor queue, but of course, the completion of the method is awaited from the CM thread, in case the component "updated" callback has thrown a configuration exception.
> Configuration updates may be missed when the component is restarting
> --------------------------------------------------------------------
>
> Key: FELIX-5242
> URL: https://issues.apache.org/jira/browse/FELIX-5242
> 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-r9
>
>
> When a component has some required dependencies, and also has a configuration dependency, then some configuration updates may be missed in the following situation:
> 1) the component has lost a required dependency: it is stopped.
> 2) the component is restarting because the lost required dependency becomes available again.
> 3) at the same time, concurrently, a configuration update is taking place.
> Then, during this racy condition, it is possible (but not systematically) that the component misses the configuration update.
> I have a test which demontrates this issue, as well as a patch. I will commit it soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)