Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 18 Jul 2014 10:26:04 +0000 (UTC)
From: "Ioannis Canellos (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12728182.1405679081310.70553.1405679164894@arcas>
In-Reply-To: <JIRA.12728182.1405679081310@arcas>
References: <JIRA.12728182.1405679081310@arcas>
Subject: [jira] [Created] (FELIX-4566) Consistency in PersistenceManager and
 Cache is not guaranteed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ioannis Canellos created FELIX-4566:
---------------------------------------

             Summary: 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


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.2#6252)