You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/10/17 17:22:00 UTC
[jira] [Commented] (GEODE-5857) Race conditions during JMX
registration and cleanup
[ https://issues.apache.org/jira/browse/GEODE-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653897#comment-16653897 ]
ASF subversion and git services commented on GEODE-5857:
--------------------------------------------------------
Commit 76420dcd93e17f009aa73ca8188d135158358323 in geode's branch refs/heads/develop from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=76420dc ]
GEODE-5857: Handle JMX race conditions during registration and cleanup
> Race conditions during JMX registration and cleanup
> ---------------------------------------------------
>
> Key: GEODE-5857
> URL: https://issues.apache.org/jira/browse/GEODE-5857
> Project: Geode
> Issue Type: Bug
> Components: jmx, management
> Reporter: Ryan McMahon
> Assignee: Ryan McMahon
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Unregistering an MBean twice results in an InstanceNotFoundException, which gets wrapped in a ManagementException and logged as a warning. This should not be a warning as an InstanceNotFoundException implies the MBean has already been unregistered, and a second unregistration is basically a no-op. The same logic applies to registration of an MBean
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)