[
https://issues.apache.org/jira/browse/FELIX-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111061#comment-16111061
]
Brandan Jeter commented on FELIX-5669:
--------------------------------------
[~cziegeler], thanks for applying that so quickly! Another difference between
your patch and mine is that the PersistenceManagerProxy classes are now
exposing their delegatees to consuming classes rather than doing the check
internally. Regardless, I don't think it's a big deal.
Other question I had: ConfigAdmin 1.8.15 is going to be released off of that R7
branch?
Thanks again.
> 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)
