[jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)
[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058226#comment-15058226 ] ASF subversion and git services commented on ARTEMIS-318: - Commit ced8ba2addfa3249d7c8db976e54a61dea4c2a3f in activemq-artemis's branch refs/heads/master from [~jbertram] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=ced8ba2 ] ARTEMIS-318 use profile JAVA_ARGS only for 'run' > Allow extra settings on command line for JVM (remote JMX & binding port > already in use when stopping broker) > - > > 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 > > 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 (/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)
[jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)
[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058227#comment-15058227 ] ASF GitHub Bot commented on ARTEMIS-318: Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/265 > Allow extra settings on command line for JVM (remote JMX & binding port > already in use when stopping broker) > - > > 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 > > 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 (/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)
[jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)
[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058197#comment-15058197 ] ASF GitHub Bot commented on ARTEMIS-318: Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/265#issuecomment-164796284 I see one problem with this... say you are running data tools (print-data for instance) and you have a large journal or paging... the memory settings won't make to the JVM. Maybe we should have a MEMORY_ARGs beyond the JAVA_ARGS.. or maybe we should also let data to use the args (since the server should be stopped anyways for any data tool)? > Allow extra settings on command line for JVM (remote JMX & binding port > already in use when stopping broker) > - > > 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 > > 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 (/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)
[jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)
[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058202#comment-15058202 ] ASF GitHub Bot commented on ARTEMIS-318: Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/265#issuecomment-164796894 the kiss version would be to be either data or run. Can you make the change? > Allow extra settings on command line for JVM (remote JMX & binding port > already in use when stopping broker) > - > > 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 > > 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 (/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)
[jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)
[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056741#comment-15056741 ] ASF GitHub Bot commented on ARTEMIS-318: GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/265 ARTEMIS-318 use profile JAVA_ARGS only for 'run' I'm not sure this is the best solution, but it has the benefit of being really simple and it solves the problem outlined in ARTEMIS-318. My only other thought here would be to use a profile per command (e.g. artemis-run.profile, artemis-stop.profile, etc.). You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-318 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/265.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #265 commit 9090ae25a7ed80e6fd7e247610d79dfe5904d286 Author: jbertram Date: 2015-12-14T21:22:32Z ARTEMIS-318 use profile JAVA_ARGS only for 'run' > Allow extra settings on command line for JVM (remote JMX & binding port > already in use when stopping broker) > - > > 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 > > 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 (/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)
[jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)
[ https://issues.apache.org/jira/browse/ARTEMIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051688#comment-15051688 ] Justin Bertram commented on ARTEMIS-318: I was able to reproduce this. As far as I can tell the problem occurs because the artemis.profile is used for both the "run" and "stop" commands and the presence of the "com.sun.management.jmxremote.port" system property causes the JVM to automatically start listening on that port in both cases. This behavior makes sense for the "run" command, but it doesn't make sense for the "stop" command. I'm still investigating potential solutions. > Allow extra settings on command line for JVM (remote JMX & binding port > already in use when stopping broker) > - > > 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 > > 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 (/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)
