You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Kirk Lund (Jira)" <ji...@apache.org> on 2020/03/13 20:52:00 UTC

[jira] [Commented] (GEODE-7739) Redundant JMX managers may not federate mbeans of other JMX managers

    [ https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059067#comment-17059067 ] 

Kirk Lund commented on GEODE-7739:
----------------------------------

The fix has been submitted as a PR for GEODE-7710.

> 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
>          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)