[
https://issues.apache.org/jira/browse/IGNITE-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017513#comment-16017513
]
Valentin Kulichenko commented on IGNITE-4831:
---------------------------------------------
My comments on the PR:
* What is the purpose of {{mbeans-disallowed.policy}} file?
* Why the catch block for {{JMException}} is changed multiple times like below?
This seems to be a redundant change.
{code}
catch (JMException e) {
if (! (e instanceof InstanceNotFoundException &&
IgniteUtils.IGNITE_DISABLE_MBEANS))
U.error(log, "Failed to unregister MBean for memory metrics: " +
memPlc.memoryMetrics().getName(), e);
}
{code}
> Add an option to disable MBeans
> -------------------------------
>
> Key: IGNITE-4831
> URL: https://issues.apache.org/jira/browse/IGNITE-4831
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 1.8
> Reporter: Valentin Kulichenko
>
> There are multiple MBeans registered by Ignite and there is no way to avoid
> their registration (in case they're not allowed for security reasons for
> example). We should have a system property that will disable MBeans.
> In addition, if MBean registration throws a {{RuntimeException}}, this
> exception is not properly handled. For example, if it happens during cache
> creation, {{createCache}} method hangs forever.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
