[jira] [Commented] (GEODE-7739) JMX managers may fail to federate mbeans for other members

["Geode Integration (Jira)" <ji...@apache.org>]

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

Geode Integration commented on GEODE-7739:
------------------------------------------

Seen in [distributed-test-openjdk8 #2688|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2688] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.16.0-build.0311/test-results/distributedTest/1654377051/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.16.0-build.0311/test-artifacts/1654377051/distributedtestfiles-openjdk8-1.16.0-build.0311.tgz].

> JMX managers may fail to federate mbeans for other members
> ----------------------------------------------------------
>
>                 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
>              Labels: GeodeOperationAPI, pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> JMX Manager may fail to federate one or more MXBeans for other members because of a race condition during startup. When ManagementCacheListener is first constructed, it is in a state that will ignore all callbacks because the field readyForEvents is false.
> ----
> 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.
> ----
> Studying the JMX code also reveals the existence of *GEODE-8012*.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)