ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-1055) Add ability to disable JMX monitoring
Date Mon, 29 Jun 2015 16:16:05 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Atri Sharma updated IGNITE-1055:
--------------------------------
    Attachment: ignite-sprint-5_ignite_1055ver2.patch

Version 2

> 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
>            Assignee: Atri Sharma
>         Attachments: ignite-sprint-5_ignite_1055ver2.patch
>
>
> 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)

Mime
View raw message