[ARTEMIS-532] Allow the control of both JMX remote ports

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.3.0
• Assignee: Justin Bertram
• Reporter: Lionel Cons
• Created: 23/May/16 13:41
• Updated: 03/Nov/16 20:40
• Resolved: 24/May/16 16:10

Description

Artemis can be configured to allow remote access to JMX. Here is the snippet found in artemis.profile:

# There might be options that you only want to enable on specifc commands, like setting a JMX port
# See https://issues.apache.org/jira/browse/ARTEMIS-318
#if [ "$1" = "run" ]; then
#  JAVA_ARGS="$JAVA_ARGS -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
#fi

This works but gives control only to the registry port, not the server port. This is not suited for firewalled environments.

The equivalent can be achieved in ActiveMQ 5 with something like:

    <managementContext>
      <managementContext connectorHost="0.0.0.0" connectorPort="6002" createConnector="true" rmiServerPort="6003">
        <property name="environment" xmlns="http://www.springframework.org/schema/beans">
          <map xmlns="http://www.springframework.org/schema/beans">
            <entry key="jmx.remote.x.password.file" value=".../etc/jmx.password" xmlns="http://www.springframework.org/schema/beans"/>
            <entry key="jmx.remote.x.access.file" value=".../etc/jmx.access" xmlns="http://www.springframework.org/schema/beans"/>
          </map>
        </property>
      </managementContext>
    </managementContext>

For more details, see http://activemq.apache.org/jmx.html.

BTW, it would be much easier to control all these JMX settings via the Artemis XML configuration file rather that Java arguments...

Issue Links

• is related to: ARTEMIS-534 Allow JMX configuration from broker.xml
• links to: GitHub Pull Request #535