[
https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-7739.
------------------------------
Fix Version/s: 1.13.0
Resolution: Fixed
Fixed by:
{noformat}
commit ff6b0c87cef91158be084a2d8ea8d9936a095e41
Author: Kirk Lund <[email protected]>
Date: Tue Mar 17 13:36:17 2020 -0700
GEODE-7710: Fix race condition in sending JMX notifications (#4808)
JMX Manager may fail to broadcast one or more JMX notifications
during startup because of a race condition involving FederatingManager
and NotificationCacheListener.
Change NotificationCacheListener to be ready upon construction.
commit 683113abe788d4925ad5a677fa82a525dd5d3a49
Author: Kirk Lund <[email protected]>
Date: Tue Mar 17 09:11:06 2020 -0700
GEODE-7710: Fix race condition in federation of MXBeans (#4807)
JMX Manager may fail to federate one or more MXBeans during startup
because of a race condition involving FederatingManager and
ManagementCacheListener.
Change ManagementCacheListener to be ready upon construction.
{noformat}
> Redundant JMX managers may not federate mbeans of other JMX managers
> --------------------------------------------------------------------
>
> Key: GEODE-7739
> URL: https://issues.apache.org/jira/browse/GEODE-7739
> Project: Geode
> Issue Type: Bug
> Components: jmx
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Debugging with JMXMBeanReconnectDUnitTest revealed this bug.
> The test starts two locators with jmx manager configured and started.
> Locator1 always has all of locator2's mbeans, but locator2 is intermittently
> missing the personal mbeans of locator1.
> I think this is caused by some sort of race condition in the code that
> creates the monitoring regions for other members in locator2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
