[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038153#comment-14038153
]
Hudson commented on HBASE-10289:
--------------------------------
SUCCESS: Integrated in HBase-TRUNK #5220 (See
[https://builds.apache.org/job/HBase-TRUNK/5220/])
HBASE-10289 Avoid random port usage by default JMX Server. Create Custome JMX
server (Qiang Tian). DOC ADDENDUM (stack: rev
b16e36a5b2650b2ce2c7686c6653c77074481115)
* src/main/docbkx/configuration.xml
> Avoid random port usage by default JMX Server. Create Custome JMX server
> ------------------------------------------------------------------------
>
> Key: HBASE-10289
> URL: https://issues.apache.org/jira/browse/HBASE-10289
> Project: HBase
> Issue Type: Improvement
> Reporter: nijel
> Assignee: Qiang Tian
> Priority: Minor
> Labels: stack
> Fix For: 0.99.0
>
> Attachments: HBASE-10289-v4.patch, HBASE-10289.patch,
> HBASE-10289_1.patch, HBASE-10289_2.patch, HBASE-10289_3.patch,
> HBase10289-master.patch, hbase10289-0.98.patch,
> hbase10289-doc_update-master.patch, hbase10289-master-v1.patch,
> hbase10289-master-v2.patch
>
>
> If we enable JMX MBean server for HMaster or Region server through VM
> arguments, the process will use one random which we cannot configure.
> This can be a problem if that random port is configured for some other
> service.
> This issue can be avoided by supporting a custom JMX Server.
> The ports can be configured. If there is no ports configured, it will
> continue the same way as now.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
