[
https://issues.apache.org/jira/browse/FELIX-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved FELIX-4566.
------------------------------------
Resolution: Fixed
Fix Version/s: configadmin-1.8.2
Committing to https://svn.apache.org/repos/asf/felix/trunk ...
M
configadmin/src/main/java/org/apache/felix/cm/impl/CachingPersistenceManagerProxy.java
Committed r1622684
> Consistency in PersistenceManager and Cache is not guaranteed
> -------------------------------------------------------------
>
> Key: FELIX-4566
> URL: https://issues.apache.org/jira/browse/FELIX-4566
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.8.2
> Reporter: Ioannis Canellos
> Assignee: Guillaume Nodet
> Fix For: configadmin-1.8.2
>
> Attachments: FELIX-4566-2.patch, FELIX-4566.patch,
> FELIX-45661-global-lock.patch
>
>
> Currently the store method in the CachingPersistenceManagerProxy performs an
> update on the PersistenceManager and then also updates the Cache.
> Since we are updating 2 resources, without any form of synchronisation its
> possible that the resources are out of sync.
> For example:
> Two threads A and B call configuration.update() on the same pid. The first
> threads calls store(), the PersistenceManager gets updated and then the
> second thread kicks in updates both PersistenceManager and the cache and
> finally the first thread updates the cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
