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

ASF subversion and git services commented on GEODE-7739:
--------------------------------------------------------

Commit 6268eafb9125f8c909462a8a029dfcc533767f55 in geode's branch 
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6268eaf ]

GEODE-7710: Fix JMXMBeanReconnectDUnitTest flakiness (#4630)

* Fix locators string delimiter
* Disable locator-to-locator MXBean validations that intermittently
  demonstrate GEODE-7739 (to be reenabled when GEODE-7739
  is fixed)

> 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
>
> I found this with the test JMXMBeanReconnectDUnitTest. 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)

Reply via email to