[GEODE-7221] Management regions never close dedicated CachePerfStats

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.10.0
• Fix Version/s: 1.11.0
• Component/s: management
• Assignee: Kirk Lund
• Reporter: Kirk Lund
• Created: 19/Sep/19 20:38
• Updated: 30/Dec/19 18:51
• Resolved: 20/Sep/19 17:40

Description

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:

InternalRegionArgs.setCachePerfStatsHolder(HasCachePerfStats)

Over in LocalRegion, the field hasOwnStats is set to false:

    if (internalRegionArgs.getCachePerfStatsHolder() != null) {
      hasOwnStats = false;
      cachePerfStats = internalRegionArgs.getCachePerfStatsHolder().getCachePerfStats();

Which results in region destroy not closing the CachePerfStats.

Issue Links

• links to: GitHub Pull Request #4072