[
https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032684#comment-17032684
]
ASF subversion and git services commented on GEODE-7739:
--------------------------------------------------------
Commit 5c8edc26ac81144f3e556fde3be9cb08f5a8fa18 in geode's branch
refs/heads/mass-test-run from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5c8edc2 ]
GEODE-7739: Federate ManagerMXBean (#4655)
* Reenable locator mbean federation validation in
JMXMBeanReconnectDUnitTest
* Fix federation of ManagerMXBean
* Remove atMost clause from await calls
> 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)
