Allow the JMX RMI server port to be hard set
--------------------------------------------
Key: AMQ-892
URL: https://issues.apache.org/activemq/browse/AMQ-892
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 4.0.2
Reporter: John Heitmann
Priority: Minor
Attachments: jmxPort.patch
When debugging a broker over the firewall with JMX it's often necessary to use
ssh tunneling. JMX uses 2 ports. The RMI registry port is what is typically
configured, but JMX also runs an RMI server on a different port-- one that's
typically chosen randomly. When you're ssh tunneling you need to know what
ports to tunnel to a priori so this is no good.
This patch adds a setting to allow the RMI server port to be set in addition to
the registry port. This is what it looks like in xml:
<managementContext connectorPort="11099" rmiServerPort="11119"
jmxDomainName="org.apache.activemq"/>
Also I snuck in a one-liner change that will create the connector if the user
configured jmx. This seems like the right thing to do, but my JMX experience is
pretty limited so it could break in something like Tomcat. Please take a close
look at that line before applying.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
