[
https://issues.apache.org/jira/browse/ZOOKEEPER-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536303#comment-13536303
]
Patrick Hunt commented on ZOOKEEPER-1605:
-----------------------------------------
JMXMP is not an option?
http://meteatamel.wordpress.com/2012/02/13/jmx-rmi-vs-jmxmp/
There might also be another way using a deterministic JMXServiceURL, but I
haven't tried it. e.g.:
http://blog.markfeeney.com/2010/10/jmx-through-ssh-tunnel.html
> Make RMI port configurable
> --------------------------
>
> Key: ZOOKEEPER-1605
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1605
> Project: ZooKeeper
> Issue Type: Improvement
> Components: jmx
> Affects Versions: 3.4.5
> Reporter: Joey Echeverria
>
> JMX uses two ports, the JMX remote port and the RMI server port. The default
> JMX agent allows you to configure the JMX remote port, via the
> com.sun.management.jmxremote.port system property, but the RMI server port is
> randomized at runtime. It's possible to create custom agent that can set the
> RMI port to a configurable value:
> http://olegz.wordpress.com/2009/03/23/jmx-connectivity-through-the-firewall/
> Making the RMI port configurable is critical to being able to monitor ZK with
> JMX through a firewall.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
