[
https://issues.apache.org/jira/browse/ARTEMIS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-534.
------------------------------------
Resolution: Duplicate
Fix Version/s: 2.4.0
> Allow JMX configuration from broker.xml
> ---------------------------------------
>
> Key: ARTEMIS-534
> URL: https://issues.apache.org/jira/browse/ARTEMIS-534
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.2.0
> Reporter: Lionel Cons
> Fix For: 2.4.0
>
>
> Currently, JMX is partially controlled from {{broker.xml}} with things like:
> {code}
> <jmx-management-enabled>true</jmx-management-enabled>
> <jmx-domain>my.org.apache.activemq</jmx-domain>
> {code}
> However, remote access configuration currently ends up in {{artemis.profile}}
> with many extra arguments such as:
> {code}
> 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"
> {code}
> It would be much better to control JMX from one place only, like ActiveMQ 5
> does via its {{<managementContext>}} element. It could appear as:
> {code}
> <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>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
