[
https://issues.apache.org/jira/browse/ARIES-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134849#comment-16134849
]
Grzegorz Grzybek commented on ARIES-1732:
-----------------------------------------
We have a race inside
{{org.apache.aries.blueprint.compendium.cm.ManagedObjectManager#register()}} too
* calling {{cm.getBundle().getBundleContext().registerService()}} schedules
{{org.apache.felix.cm.impl.ConfigurationManager.ManagedServiceUpdate}} which
then calls
{{org.apache.aries.blueprint.compendium.cm.ManagedObjectManager.ConfigurationWatcher#updated()}}
in CM UpdateThread
* a bit later, we call {{cm.updated(config)}} after getting the CM
configuration manually
> blueprint-cm - race condition
> -----------------------------
>
> Key: ARIES-1732
> URL: https://issues.apache.org/jira/browse/ARIES-1732
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Paolo Antinori
> Assignee: Grzegorz Grzybek
>
> There is a possible race condition in
> `org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder` and
> `org.apache.aries.blueprint.compendium.cm.ManagedObjectManager`
> There are situations where `ConfigAdmin` service might not be available and
> returns `null` when queried for the initial `config`.
> In other cases instead, `CmPropertyPlaceholder` receives updates from
> `ConfigAdmin` thread even before it has completed it's initialization.
> The code doesn't discriminate if `config` is `null` or not, and treats any
> value as valid, marking `CmPropertyPlaceholder` instance as initialized.
> This leads to spotty errors.
> The suggested fix, that simply prevents that `update(null)` invocation mark
> the `CmPropertyPlaceholder` instance as initialized, addresses the issue.
> Code here:
> https://github.com/apache/aries/compare/trunk...paoloantinori:ENTESB-7141?expand=1
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
