You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2015/06/25 16:24:04 UTC
[jira] [Updated] (IGNITE-1055) Add ability to disable JMX
monitoring
[ https://issues.apache.org/jira/browse/IGNITE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Setrakyan updated IGNITE-1055:
--------------------------------------
Component/s: newbie
general
> Add ability to disable JMX monitoring
> -------------------------------------
>
> Key: IGNITE-1055
> URL: https://issues.apache.org/jira/browse/IGNITE-1055
> Project: Ignite
> Issue Type: Improvement
> Components: general, newbie
> Reporter: Yakov Zhdanov
>
> It seems that {{ignite.sh | bat}} will always try to find free port to launch JMX monitoring.
> See places where {{org.apache.ignite.internal.util.portscanner.GridJmxPortFinder}} is launched in {{sh}} and {{bat}}.
> I think that ability to skip JMX init should be provided (via command line parameter to {{sh}} and {{bat}}.
> How about: {{$ ignite.sh -nojmx ......}}?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)