Lionel Cons created ARTEMIS-532:
-----------------------------------
Summary: Allow the control of both JMX remote ports
Key: ARTEMIS-532
URL: https://issues.apache.org/jira/browse/ARTEMIS-532
Project: ActiveMQ Artemis
Issue Type: Improvement
Reporter: Lionel Cons
Artemis can be configured to allow remote access to JMX. Here is the snippet
found in {{artemis.profile}}:
{code}
# 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
{code}
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:
{code}
<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>
{code}
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...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
