Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 25 Aug 2011 12:19:31 +0000 (UTC)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: 
 <1267583839.13363.1314274771657.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1335826757.37274.1313336847133.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (APLO-73) Service does not stop, Control-C in
 console does not work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hiram Chirino resolved APLO-73.
-------------------------------

    Resolution: Fixed

> 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