[
https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892837#comment-13892837
]
Steve Loughran commented on HADOOP-10136:
-----------------------------------------
# how would this get wired up in an application?
# what would be very nice would be for the JMXServer to extend
{{AbstractService}}, and so share the same lifecycle. Any YARN composite
service could simply add it as a child & hook it into its lifecycle
> 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.5#6160)
