felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandan Jeter (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FELIX-5669) Registering a PersistenceManager causes duplicate caches
Date Wed, 02 Aug 2017 14:55:00 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111061#comment-16111061
] 

Brandan Jeter edited comment on FELIX-5669 at 8/2/17 2:54 PM:
--------------------------------------------------------------

[~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 questions I had: ConfigAdmin 1.8.15 is going to be released off of that R7 branch? And
when do you think you guys are going to release it and do you know the earliest version of
Karaf that it will be in?

Thanks again.


was (Author: brandan.jeter):
[~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? And
when do you think you guys are going to release it and do you know the earliest version of
Karaf that it will be in?

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)

Mime
View raw message