[
https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105492#comment-15105492
]
Hiram Chirino commented on ARTEMIS-318:
---------------------------------------
For 1.2 I've update this so that the generated profile scripts contain an
example of how to set JVM options that are only enabled for the run command.
This should be a cleaner way to resolve this issue.
> 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
> Environment: all
> Reporter: Michal Toth
> Assignee: Justin Bertram
> Labels: features
> Fix For: 1.1.1
>
>
> 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.4#6332)
