[ https://issues.apache.org/activemq/browse/AMQ-892?page=comments#action_36832 ] John Heitmann commented on AMQ-892: -----------------------------------
There are at least 2 unfortunate issues with the out-of-the-box 1.5 JMX config: the rmi registry isn't able to use a secure transport, and the rmi server port is not able to be fixed. My patch addresses the second, and I think you're right in that it's better to use the normal jmx properties config rather than the xbean xml. I'll redo this patch and mimic an out-of-the-box agent as described by one of the JMX developers here: http://blogs.sun.com/roller/page/lmalventosa/20060602 That will have the nice benefit of also allowing a secure registry, which is something my group will need shortly anyway. > 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
