Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CAB5E100B5 for ; Sat, 2 Nov 2013 21:57:17 +0000 (UTC) Received: (qmail 79662 invoked by uid 500); 2 Nov 2013 21:57:17 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 79623 invoked by uid 500); 2 Nov 2013 21:57:17 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 79614 invoked by uid 99); 2 Nov 2013 21:57:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Nov 2013 21:57:17 +0000 Date: Sat, 2 Nov 2013 21:57:17 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-1065) Provide startup option to flush journal to store then exit the broker MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated AMQ-1065: ----------------------------- Assignee: (was: Adrian Co) > Provide startup option to flush journal to store then exit the broker > --------------------------------------------------------------------- > > Key: AMQ-1065 > URL: https://issues.apache.org/jira/browse/AMQ-1065 > Project: ActiveMQ > Issue Type: Wish > Components: Broker > Affects Versions: 5.0.0 > Reporter: jk@penguinsfan.com > Fix For: AGING_TO_DIE > > > This is a "wish" for a command line argument that will flush the journal to the database and quit. > This makes it possible to: > 1. Do some kinds of message administration / emergency fixing in SQL. > 2. Upgrade even if there are incompatible changes by first flushing the journal and then applying the appropriate SQL change script to the database. > 3. Switch the kind of journaling, switch to no journaling, etc. > Jason -- This message was sent by Atlassian JIRA (v6.1#6144)