Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Message-ID: <3193617.1156234103103.JavaMail.jira@brutus>
Date: Tue, 22 Aug 2006 01:08:23 -0700 (PDT)
From: "John Heitmann (JIRA)" <jira@apache.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Created: (AMQ-892) Allow the JMX RMI server port to be hard
 set
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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