activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guy Allard (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (APLO-73) Service does not stop, Control-C in console does not work
Date Mon, 15 Aug 2011 19:59:27 GMT

     [ https://issues.apache.org/jira/browse/APLO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guy Allard reopened APLO-73:
----------------------------


Hiram - I get the same results with both of these:

a) apache-apollo-1.0-20110815.061655-170-unix-distro.tar.gz

b) SVN checkout of:

Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1157681

Can I give you any other information?


> Service does not stop, Control-C in console does not work
> ---------------------------------------------------------
>
>                 Key: APLO-73
>                 URL: https://issues.apache.org/jira/browse/APLO-73
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta3, 1.0-beta4
>         Environment: Ubuntu 11.04
> Both beta 3 and beta4 installed from binaries.
> Running as a normal user (not root).
>            Reporter: Guy Allard
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> 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: http://www.atlassian.com/software/jira

        

Mime
View raw message