[jira] [Created] (IGNITE-1055) Add ability to disable JMX monitoring

[Anton Vinogradov (Jira)]

Yakov Zhdanov created IGNITE-1055:
-------------------------------------

             Summary: Add ability to disable JMX monitoring
                 Key: IGNITE-1055
                 URL: https://issues.apache.org/jira/browse/IGNITE-1055
             Project: Ignite
          Issue Type: Improvement
            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)

[dsetrakyan]

I have added this ticket to the "newbie" list, so new committers could try
to tackle it.

D.

On Thu, Jun 25, 2015 at 7:06 AM, Yakov Zhdanov (JIRA) <[hidden email]>
wrote:

> Yakov Zhdanov created IGNITE-1055:
> -------------------------------------
>
>              Summary: Add ability to disable JMX monitoring
>                  Key: IGNITE-1055
>                  URL: https://issues.apache.org/jira/browse/IGNITE-1055
>              Project: Ignite
>           Issue Type: Improvement
>             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)
>