[jira] [Updated] (GEODE-7221) Management regions never close dedicated CachePerfStats

["Kirk Lund (Jira)" <ji...@apache.org>]

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

Kirk Lund updated GEODE-7221:
-----------------------------
    Affects Version/s: 1.10.0
                       1.0.0-incubating
                       1.1.0
                       1.1.1
                       1.2.0
                       1.3.0
                       1.2.1
                       1.4.0
                       1.5.0
                       1.6.0
                       1.7.0
                       1.8.0
                       1.9.0
                       1.9.1

> Management regions never close dedicated CachePerfStats
> -------------------------------------------------------
>
>                 Key: GEODE-7221
>                 URL: https://issues.apache.org/jira/browse/GEODE-7221
>             Project: Geode
>          Issue Type: Bug
>          Components: management
>    Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.10.0
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Major
>
> The FederatingManager and LocalManager classes create the monitoring and notification regions for management of each member. They are constructing injecting HasCachePerfStats instances with their own dedicated instances of CachePerfStats into InternalRegionArgs:
> {noformat}
> InternalRegionArgs.setCachePerfStatsHolder(HasCachePerfStats)
> {noformat}
> Over in LocalRegion, the field hasOwnStats is set to false:
> {noformat}
>     if (internalRegionArgs.getCachePerfStatsHolder() != null) {
>       hasOwnStats = false;
>       cachePerfStats = internalRegionArgs.getCachePerfStatsHolder().getCachePerfStats();
> {noformat}
> Which results in region destroy not closing the CachePerfStats.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)