Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 9 Apr 2015 20:07:14 +0000 (UTC)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: <JIRA.12766886.1421081998000.45234.1428610034069@Atlassian.JIRA>
In-Reply-To: <JIRA.12766886.1421081998000@Atlassian.JIRA>
References: <JIRA.12766886.1421081998000@Atlassian.JIRA>
 <JIRA.12766886.1421081998829@arcas>
Subject: [jira] [Comment Edited] (APLO-373) Apollo service fails to stop
 properly with purge_on_startup="true"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hiram Chirino edited comment on APLO-373 at 4/9/15 8:06 PM:
------------------------------------------------------------

Perhaps the broker should know not to delete the pid files tho.


was (Author: chirino):
Please attach patch with your fix. thx!

> Apollo service fails to stop properly with purge_on_startup="true"
> ------------------------------------------------------------------
>
>                 Key: APLO-373
>                 URL: https://issues.apache.org/jira/browse/APLO-373
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>            Reporter: Andrew Lin
>
> Steps to reproduce:
>   * Set up a broker with the "purge_on_startup" option set to "true"
>   * Use "apollo-broker-service start" to start the broker
>   * Use "apollo-broker-service stop"
> Expected behavior: apollo process is stopped
> Observed behavior: apollo process is not stopped
> I'm pretty sure the problem is that the service script puts its pidfile in the data directory, which is purged by apollo on startup.  Hacking the script to put the pidfile outside the data directory does solve my problem.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)