activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-532) Allow the control of both JMX remote ports
Date Tue, 24 May 2016 06:29:12 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297762#comment-15297762
] 

Lionel Cons commented on ARTEMIS-532:
-------------------------------------

At first look, it seems that {{-Dcom.sun.management.jmxremote.rmi.port=1098}} should work.
See http://stackoverflow.com/questions/25124148/connect-to-remote-jboss-with-jmx-behind-a-firewall.

> 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
>    Affects Versions: 1.2.0
>            Reporter: Lionel Cons
>            Assignee: Justin Bertram
>             Fix For: 1.3.0
>
>
> 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)

Mime
View raw message