Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.216.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1321630192917-4083655.post@n4.nabble.com>
References: <1321630192917-4083655.post@n4.nabble.com>
Date: Wed, 23 Nov 2011 10:22:37 +0000
Message-ID: 
 <CAH+vQmNTD4pOPyOkHKskA4Y5k0CL-1b4f41KQKJde3rroqXGHQ@mail.gmail.com>
Subject: Re: Live Broker and KahaDB on NFS4
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

In that case, the expectation from the broker is that disk io will
result in an IOException and the default behavior in that case is to
stop the broker. Look at:
http://activemq.apache.org/configurable-ioexception-handling.html

On restart, once the partition is available, the broker will recover
(replay the journal) from its last valid checkpoint.


On 18 November 2011 15:29, Jeremy Deane <jdeane@plymouthrock.com> wrote:
> What are the implications to a live broker where the mount point containing
> the KahaDB fails? And what is the recommended process to recover from such a
> failure?
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Live-Broker-and-KahaDB-on-NFS4-tp4083655p4083655.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
http://fusesource.com
http://blog.garytully.com