[
https://issues.apache.org/jira/browse/FELIX-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112247#comment-16112247
]
Carsten Ziegeler commented on FELIX-5669:
-----------------------------------------
[~brandan.jeter] Yes, right, the deletagee is now accessible - but as these are
all internal classes I think this is fine.
I've backported the fix to the 1.8.x branch in revision 1803950 - it would be
great if you can give it a quick lock. I can then start the 1.8.16 release, so
it should be available next week.
I don't know when Karaf will pick it up though
> Registering a PersistenceManager causes duplicate caches
> --------------------------------------------------------
>
> Key: FELIX-5669
> URL: https://issues.apache.org/jira/browse/FELIX-5669
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.8.12
> Reporter: Brandan Jeter
> Assignee: Carsten Ziegeler
> Fix For: configadmin-1.8.16
>
>
> 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)
