You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Vinay (JIRA)" <ji...@apache.org> on 2013/11/30 08:47:35 UTC
[jira] [Updated] (HADOOP-10136) Custom JMX server to avoid random
port usage by default JMX Server
[ https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinay updated HADOOP-10136:
---------------------------
Attachment: HADOOP-10136.patch
Attaching the initial patch.
Please review and let me know your feedback
> Custom JMX server to avoid random port usage by default JMX Server
> ------------------------------------------------------------------
>
> Key: HADOOP-10136
> URL: https://issues.apache.org/jira/browse/HADOOP-10136
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Vinay
> Assignee: Vinay
> Attachments: HADOOP-10136.patch
>
>
> If any of the java process want to enable the JMX MBean server then following VM arguments needs to be passed.
> {code}
> -Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=14005
> -Dcom.sun.management.jmxremote.local.only=false
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false{code}
> But the issue here is this will use one more random port other than 14005 while starting JMX.
> This can be a problem if that random port is used for some other service.
> So support a custom JMX Server through which random port can be avoided.
--
This message was sent by Atlassian JIRA
(v6.1#6144)