[
https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-7739:
-----------------------------
Description:
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.
It's possible that the jmx manager that hits this bug might fail to have mbeans
for servers as well as other locators but I haven't seen a test case for this
scenario.
The exposure of this bug means that a user running more than one locator might
have a locator that is missing one or more mbeans for the cluster.
was:
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.
> 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.
> It's possible that the jmx manager that hits this bug might fail to have
> mbeans for servers as well as other locators but I haven't seen a test case
> for this scenario.
> The exposure of this bug means that a user running more than one locator
> might have a locator that is missing one or more mbeans for the cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
