[
https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491433#comment-15491433
]
Arshad Mohammad commented on ZOOKEEPER-1971:
--------------------------------------------
If we throw exception many exiting zookeeper applications start failing because
of port conflict. Exception was not thrown to make the existing applications
work as before. But there are many other problem with this approach even the
normal jmx env is not started.
I will disable custom jxm by default in the code, but enable custom jmx from
zkServer.sh by default then we can throw exception in case of the custom jxm
env fails. I will update the patch for this.
> Make JMX remote monitoring port configurable
> --------------------------------------------
>
> Key: ZOOKEEPER-1971
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.5.0
> Environment: All
> Reporter: Biju Nair
> Assignee: Arshad Mohammad
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch,
> zookeeperAdmin.pdf, zookeeperJMX.pdf
>
>
> This is a follow-up item from ZOOKEEPER-1948.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
