activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3082) Broker doesn't stop using the activemq script if the JMX port is changed
Date Sun, 07 Oct 2012 13:28:03 GMT

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

Claus Ibsen commented on AMQ-3082:
----------------------------------

Yeah I see this on the 5.7.0 release
{code}
davsclaus:/opt/amq2$ bin/activemq stop
INFO: Using default configuration
(you can configure options in one of these file: /etc/default/activemq /Users/davsclaus/.activemqrc)

INFO: Invoke the following command to create a configuration file
bin/activemq setup [ /etc/default/activemq | /Users/davsclaus/.activemqrc ]

INFO: Using java '/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin/java'
INFO: Waiting at least 30 seconds for regular process termination of pid '47996' : 
Java Runtime: Apple Inc. 1.6.0_35 /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
  Heap sizes: current=1044352k  free=1042987k  max=1044352k
    JVM args: -Xms1G -Xmx1G -Djava.util.logging.config.file=logging.properties -Dactivemq.classpath=/opt/amq2/conf;
-Dactivemq.home=/opt/amq2 -Dactivemq.base=/opt/amq2 -Dactivemq.conf=/opt/amq2/conf -Dactivemq.data=/opt/amq2/data
Extensions classpath:
  [/opt/amq2/lib,/opt/amq2/lib/camel,/opt/amq2/lib/optional,/opt/amq2/lib/web,/opt/amq2/lib/extra]
ACTIVEMQ_HOME: /opt/amq2
ACTIVEMQ_BASE: /opt/amq2
ACTIVEMQ_CONF: /opt/amq2/conf
ACTIVEMQ_DATA: /opt/amq2/data
Connecting to pid: 47996
ERROR: java.lang.IllegalArgumentException: JMX URL already specified.
java.lang.IllegalArgumentException: JMX URL already specified.
	at org.apache.activemq.console.command.AbstractJmxCommand.handleOption(AbstractJmxCommand.java:348)
	at org.apache.activemq.console.command.ShutdownCommand.handleOption(ShutdownCommand.java:156)
	at org.apache.activemq.console.command.AbstractCommand.parseOptions(AbstractCommand.java:73)
	at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:45)
	at org.apache.activemq.console.command.AbstractJmxCommand.execute(AbstractJmxCommand.java:385)
	at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:148)
	at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
	at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:90)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
	at org.apache.activemq.console.Main.main(Main.java:115)
.INFO: There are no brokers to stop.
............................
INFO: Regular shutdown not successful,  sending SIGKILL to process with pid '47996'
{code}
                
> Broker doesn't stop using the activemq script if the JMX port is changed
> ------------------------------------------------------------------------
>
>                 Key: AMQ-3082
>                 URL: https://issues.apache.org/jira/browse/AMQ-3082
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.1
>         Environment: CentOS 5.4 64 bits
>            Reporter: Iker Jimenez
>            Assignee: Claus Ibsen
>
> I have two activemq instances on the same machine. One running on all the default port
settings and the other one on the following ports:
> Changed to the second activemq instance:
> in bin/activemq:
> ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://localhost:1100/jmxrmi"
> in conf/activemq.xml
> <managementContext createConnector="true" connectorPort="1100" jmxDomainName="broker2"/>
> ...
> <transportConnector name="openwire" uri="tcp://0.0.0.0:61617"/>
> in conf/jetty.xml
> <property name="port" value="8162" />
> So when I execute bin/activemq start:
> ...
>  INFO | JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1100/jmxrmi
>  INFO | Listening for connections at: tcp://myhostname:61617
> ...
> When I try to stop it, bin/activemq stop:
> ...
> INFO: There are no brokers to stop.
> .
> INFO: Regular shutdown not successful,  sending SIGKILL to process with pid '26137'
> I added some logging to the script to discover that it was doing this call:
> /usr/bin/java -Dactivemq.classpath="/home/myuser/activeMQ2/apache-activemq-5.4.1/conf;"
-Dactivemq.home="/home/myuser/activeMQ2/apache-activemq-5.4.1" -Dactivemq.base="/home/myuser/activeMQ2/apache-activemq-5.4.1"
-jar "/home/myuser/activeMQ2/apache-activemq-5.4.1/bin/run.jar" stop --jmxurl service:jmx:rmi:///jndi/rmi://localhost:1100/jmxrmi
> This doesn't seem to find the JMX service in the specified location, even though it is
the URL that was printed at start up (See log above).
> All I wanted to have is two instances running on the same box to test a cluster configuration,
but starting/stopping them correctly with the scripts seem to be a pain. A simple kill to
the process PID works much better.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message