[
https://issues.apache.org/jira/browse/ZOOKEEPER-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053479#comment-14053479
]
nijel commented on ZOOKEEPER-1948:
----------------------------------
bq.Is this related to ZOOKEEPER-1346?
>From the discussion i understand the issue ZOOKEEPER-1346 is for supporting a
>new REST interface for 4wls.
Even after this implementation users will have option to use the remote JMX
monitoring by enabling JMX server.
But if the remote monitoring is enabled, then it will use 2 extra ports, one of
which is random.
So my suggestion was to implement RMI based custom JMX server where the ports
can be configured.
BTW
this issue (Enable JMX remote monitoring) is because of missing arguement
*com.sun.management.jmxremote.authenticate*=false
As per code remote monitoring should be enabled since default value of
JMXLOCALONLY=false.
I added this property as -D args and it worked. i think need to add this in
script
> Enable JMX remote monitoring
> ----------------------------
>
> Key: ZOOKEEPER-1948
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1948
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Environment: All
> Reporter: Biju Nair
>
> The zooker server start up script includes the option to enable jmx
> monitoring but only locally. Can we update the script so that remote
> monitoring can also be enabled which will help in data collection and
> monitoring through a centralized monitoring tool.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
