[FELIX-4566] Consistency in PersistenceManager and Cache is not guaranteed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: configadmin-1.8.2
• Fix Version/s: configadmin-1.8.2
• Component/s: Configuration Admin
• Assignee: Guillaume Nodet
• Reporter: Ioannis Canellos
• Created: 18/Jul/14 10:24
• Updated: 15/Apr/15 15:12
• Resolved: 05/Sep/14 11:29

Description

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.

Issue Links

• breaks: KARAF-3668 ManagedServiceFactory update is not called after restart
• relates to: KARAF-3204 Avoid calls to Configuration#setBundleLocation(null) which are not needed