Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
org.apache.felix.dependencymanager-r1
-
None
Description
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.