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 2018/10/24 20:53:00 UTC
[jira] [Updated] (GEODE-5924) JMX manager may fail to register for
Alerts with all members
[ https://issues.apache.org/jira/browse/GEODE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirk Lund updated GEODE-5924:
-----------------------------
Affects Version/s: 1.0.0-incubating
1.1.0
1.1.1
1.2.0
1.3.0
1.2.1
1.4.0
1.5.0
1.6.0
1.7.0
> JMX manager may fail to register for Alerts with all members
> ------------------------------------------------------------
>
> Key: GEODE-5924
> URL: https://issues.apache.org/jira/browse/GEODE-5924
> Project: Geode
> Issue Type: Bug
> Components: management
> Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0, 1.6.0, 1.7.0
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Priority: Major
>
> JMX manager may fail to register for Alerts with all members.
> Invoking DistributedSystemMXBean.changeAlertLevel(String alertLevel) seems to work around the problem.
> Hosting the JMX manager within a Locator also seems to work around this which suggests there is a race condition involving ManagerStartupMessage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)