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-3058) Stopping ActiveMQ won´t work if the ActiveMQ path contains a whitespace.
Date Sat, 02 Nov 2013 20:43:17 GMT

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

Claus Ibsen commented on AMQ-3058:
----------------------------------

It is not a good idea either to use spaces in path names.

> Stopping ActiveMQ won´t work if the ActiveMQ path contains a whitespace.
> ------------------------------------------------------------------------
>
>                 Key: AMQ-3058
>                 URL: https://issues.apache.org/jira/browse/AMQ-3058
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.1
>         Environment: Mac OS 10.6.5
>            Reporter: Julian Quindt
>            Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The script command "./activemq stop" fails when the path to ActiveMQ contains a whitespace.
The broker continues to execute. Find a CLI output reproducing this bug below:
> zaphod:Software Jule$ cd /Users/Jule/White\ Space/
> zaphod:White Space Jule$ cd bin
> zaphod:bin Jule$ ./activemq start
> INFO: Using default configuration
> (you can configure options in one of these file: /etc/default/activemq /Users/Jule/.activemqrc)
> INFO: Invoke the following command to create a configuration file
> ./activemq setup [ /etc/default/activemq | /Users/Jule/.activemqrc ]
> INFO: Using java '/System/Library/Frameworks/JavaVM.framework/Home/bin/java'
> INFO: Starting - inspect logfiles specified in logging.properties and log4j.properties
to get details
> INFO: pidfile created : '/Users/Jule/White' (pid '3506')
> zaphod:bin Jule$ echo juleq: Waiting for broker to come up...
> juleq: Waiting for broker to come up...
> zaphod:bin Jule$ ./activemq stop
> INFO: Using default configuration
> (you can configure options in one of these file: /etc/default/activemq /Users/Jule/.activemqrc)
> INFO: Invoke the following command to create a configuration file
> ./activemq setup [ /etc/default/activemq | /Users/Jule/.activemqrc ]
> INFO: Using java '/System/Library/Frameworks/JavaVM.framework/Home/bin/java'
> ActiveMQ not running
> zaphod:bin Jule$ ps -A | grep ctive
>  3506 ttys000    0:11.78 /System/Library/Frameworks/JavaVM.framework/Home/bin/java -Xms256M
-Xmx256M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties
-Dcom.sun.management.jmxremote -Dactivemq.classpath=/Users/Jule/White Space/conf; -Dactivemq.home=/Users/Jule/White
Space -Dactivemq.base=/Users/Jule/White Space -jar /Users/Jule/White Space/bin/run.jar start
>  3528 ttys000    0:00.00 grep ctive
> zaphod:bin Jule$ echo "juleq: Broker is still running :-(..."
> juleq: Broker is still running :-(...
> zaphod:bin Jule$ 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message