[ARTEMIS-534] Allow JMX configuration from broker.xml

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.2.0
• Fix Version/s: 2.4.0
• Assignee: Unassigned
• Reporter: Lionel Cons
• Created: 24/May/16 06:45
• Updated: 16/Oct/17 16:29
• Resolved: 16/Oct/17 16:29

Description

Currently, JMX is partially controlled from broker.xml with things like:

<jmx-management-enabled>true</jmx-management-enabled>
<jmx-domain>my.org.apache.activemq</jmx-domain>

However, remote access configuration currently ends up in artemis.profile with many extra arguments such as:

JAVA_ARGS="$JAVA_ARGS -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.rmi.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.password.file=${ARTEMIS_INSTANCE}/etc/jmx.password -Dcom.sun.management.jmxremote.access.file=${ARTEMIS_INSTANCE}/etc/jmx.access"

It would be much better to control JMX from one place only, like ActiveMQ 5 does via its <managementContext> element. It could appear as:

<jmx enabled="true" jmxremote="true">
  <domain>my.org.apache.activemq</domain>
  <connect-port>1099</connect-port>
  <rmi-port>1098</rmi-port>
  <password-file>${artemis.instance}/etc/jmx.password</password-file>
  <access-file>${artemis.instance}/etc/jmx.access</access-file>
</jmx>

Issue Links

• duplicates: ARTEMIS-1463 Implement rbac of management objects
• relates to: ARTEMIS-532 Allow the control of both JMX remote ports