Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.0-beta3, 1.0-beta4
-
None
-
Ubuntu 11.04
Both beta 3 and beta4 installed from binaries.
Running as a normal user (not root).
Description
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