activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guy Allard (JIRA)" <>
Subject [jira] [Created] (APLO-73) Service does not stop, Control-C in console does not work
Date Sun, 14 Aug 2011 15:47:27 GMT
Service does not stop, Control-C in console does not work

                 Key: APLO-73
             Project: ActiveMQ Apollo
          Issue Type: Bug
          Components: apollo-broker
    Affects Versions: 1.0-beta4, 1.0-beta3
         Environment: Ubuntu 11.04
Both beta 3 and beta4 installed from binaries.
Running as a normal user (not root).
            Reporter: Guy Allard

Have been running beta2, and decided to upgrade this morning.  I started with beta4.

1) When a broker is run from the command line, control-c fails to stop the broker
2) When a broker is run as a service from /etc/init.d the 'stop' command fails with 'Could
not stop process ####'.

In both cases, only 'kill -9' has an effect.

apollo.log repeatedly shows messages like:

2011-08-14 10:57:45,951 | INFO  | stopping config monitor is taking a long time (31 seconds).
Waiting on stop org.apache.activemq.apollo.util.FileMonitor@6c533246 | org.apache.activemq.apollo.util.LoggingTracker
| hawtdispatch-DEFAULT-1

Same behavior with beta3.

Brokers are running with minimal configuration changes:

a) Disable authentication
b) Connector port number changes
c) log4j tweaks

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message