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

Justin Bertram commented on ARTEMIS-318:
----------------------------------------

At this point I would consider this a user-education issue.  If you want to 
enabled remote JMX connectivity then you should do it by uncommenting the 
necessary lines from the "profile" (e.g. artemis.profile) after the broker 
instance is created rather than through the the {{\--java-options}} switch when 
creating the instance.  The stuff specified in {{\--java-options}} is forced 
onto the command-line no matter what, but the profile has a conditional 
statement that will only add the JMX stuff for the {{run}} command.

Eventually we should refactor the handling of the Java command arguments.  
Currently they are spread across both the profile and the actual executable 
script.

> Can't stop broker when remote JMX enabled
> -----------------------------------------
>
>                 Key: ARTEMIS-318
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-318
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.1.0, 1.2.0
>         Environment: all
>            Reporter: Michal Toth
>            Assignee: Justin Bertram
>              Labels: features
>             Fix For: 1.3.0
>
>
>  I have been using remote JMX with Artemis for few weeks so far,
> but lately, I have noticed, that I am not able to shutdown the Artemis 
> gracefully via 'artemis stop' nor 'artemis-service stop' when JMX is set up.
> Here is my scenario:
> 1) Add system properties to java (<broker_instance>/etc/artemis.profile):
> 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 "
> 2) Start the broker
> 3) Do JMX "queries", send messages, everything works fine
> 4) bin/artemis stop
> Error: Exception thrown by the agent : java.rmi.server.ExportException: Port 
> already in use: 1099; nested exception is:
>         java.net.BindException: Address already in use
> It does not matter what port number I use.
> Error: Exception thrown by the agent : java.rmi.server.ExportException: Port 
> already in use: 3099; nested exception is:
>         java.net.BindException: Address already in use
> 5) I have kill the artemis process (SIGTERM is sufficient) to stop it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to