You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/08/02 09:07:00 UTC

[jira] [Assigned] (FELIX-5669) Registering a PersistenceManager causes duplicate caches

     [ https://issues.apache.org/jira/browse/FELIX-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reassigned FELIX-5669:
---------------------------------------

    Assignee: Carsten Ziegeler

> Registering a PersistenceManager causes duplicate caches
> --------------------------------------------------------
>
>                 Key: FELIX-5669
>                 URL: https://issues.apache.org/jira/browse/FELIX-5669
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: configadmin-1.8.12
>            Reporter: Brandan Jeter
>            Assignee: Carsten Ziegeler
>             Fix For: configadmin-1.9.0
>
>
> When registering a PersistenceManager, the next call to a method in ConfigurationManager will call getPersistenceManagers(). Instead of preserving the existing CachingPersistenceManagerProxy that wraps the default FilePersistenceManager, ConfigurationManager creates a brand new one. But previous Configuration objects still have reference to the old CachingPersistenceManagerProxy, so when one of them gets deleted/updated it does not get deleted/updated in the ConfigurationManager's reference.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)