Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 046DB1090F for ; Wed, 29 Jan 2014 07:30:15 +0000 (UTC) Received: (qmail 51448 invoked by uid 500); 29 Jan 2014 07:30:13 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 51297 invoked by uid 500); 29 Jan 2014 07:30:11 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 51275 invoked by uid 99); 29 Jan 2014 07:30:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jan 2014 07:30:10 +0000 Date: Wed, 29 Jan 2014 07:30:10 +0000 (UTC) From: "nijel (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated HBASE-10289: -------------------------- Attachment: HBASE-10289_2.patch Updated the patch > 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 > Priority: Minor > Fix For: 0.99.0 > > Attachments: HBASE-10289.patch, HBASE-10289_1.patch, HBASE-10289_2.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.1.5#6160)