You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Michal Toth (JIRA)" <ji...@apache.org> on 2017/03/27 13:30:41 UTC

[jira] [Commented] (ARTEMIS-318) Can't stop broker when remote JMX enabled

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

Michal Toth commented on ARTEMIS-318:
-------------------------------------

I am not 100% sure if this fix has affected artemis.profile & bin/artemis files, but now, when you create a broker instance with appended java-options, they got into "exec java $JAVA_OPTS..."  in bin/artemis. If you put there jmx.remote and specify port 1099, you will get with second execution of this command on the same machine Binding exception, port 1099 already in use. (for example: Broker is running, print journal data "bin/artemis print data" -> BindingException.)
This seems like a regression to me.

> 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)