activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Resolved: (AMQ-892) Allow the JMX RMI server port to be hard set
Date Fri, 25 Aug 2006 15:29:23 GMT
     [ ]

james strachan resolved AMQ-892.

    Fix Version/s: 4.1
       Resolution: Fixed

Patch applied John thanks!

I've been thinking we should encourage folks to use the standard JMX configuration system
properties and an optional security manager and policy file as opposed to the xbean.xml stuff
- but its good to keep that working fine for folks who want to use it.

> Allow the JMX RMI server port to be hard set
> --------------------------------------------
>                 Key: AMQ-892
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 4.0.2
>            Reporter: John Heitmann
>            Priority: Minor
>             Fix For: 4.1
>         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:
For more information on JIRA, see:


View raw message