[ https://issues.apache.org/jira/browse/HADOOP-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524811#comment-14524811 ]
Hadoop QA commented on HADOOP-10136: ------------------------------------ \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:red}-1{color} | patch | 0m 1s | The patch command could not apply the patch during dryrun. | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12627604/HADOOP-10136.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / f1a152c | | Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/6334/console | This message was automatically generated. > 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: Vinayakumar B > Assignee: Vinayakumar B > Attachments: HADOOP-10136.patch, HADOOP-10136.patch, > 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.3.4#6332)