activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-318) Allow extra settings on command line for JVM (remote JMX & binding port already in use when stopping broker)
Date Tue, 15 Dec 2015 15:21:46 GMT

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

Mime
View raw message