Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 8731 invoked from network); 23 Feb 2007 05:55:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Feb 2007 05:55:06 -0000 Received: (qmail 28417 invoked by uid 500); 23 Feb 2007 05:55:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 28395 invoked by uid 500); 23 Feb 2007 05:55:14 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 28386 invoked by uid 99); 23 Feb 2007 05:55:14 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 21:55:14 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of james.strachan@gmail.com designates 64.233.182.191 as permitted sender) Received: from [64.233.182.191] (HELO nf-out-0910.google.com) (64.233.182.191) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 21:55:03 -0800 Received: by nf-out-0910.google.com with SMTP id y38so768805nfb for ; Thu, 22 Feb 2007 21:54:42 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XjE6qfPmTCiN8Ypbg0C0TacJ0l+ryWOWyudZaiee4Hm9Mp4h0K7HIaQ6ZVPkCTnUPhbAT8aVc4z8BZdGDbpHklpR2P81H4p1KcQ0AvnTsgtV2mPQi9j7Gq0ReqJRCQRveiepuO6XXcekaYAOEBbXOlH5k4qG/+xla5cWO6koIAU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=F6mx85qLujS1p08apv7Ss9eo2rx86c0jmstJ2p/QI8DRZBG+g+kDFzhDgDUSzuCJ2n+WOWHZ1H4olYg02xDRl3cq3ZXpwNE0OPTOL1npUcXzdNyOdr3i02eOJIQQhsUMWzHZcYObqUMXu6smUexdcFGhwT9DBuoi813185hW88E= Received: by 10.78.204.7 with SMTP id b7mr134890hug.1172210082081; Thu, 22 Feb 2007 21:54:42 -0800 (PST) Received: by 10.78.155.7 with HTTP; Thu, 22 Feb 2007 21:54:42 -0800 (PST) Message-ID: Date: Fri, 23 Feb 2007 05:54:42 +0000 From: "James Strachan" To: users@activemq.apache.org Subject: Re: Recover a failed Broker's Journal (by Database of Another Broker) In-Reply-To: <9109462.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9109462.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org On 2/22/07, spiderman2 wrote: > > I'm looking into clustered HA deployments with zero message loss under one > point-of-failure. > > My best options seem to be: > A) Network of Brokers with fast journaling and jdbc persistance Networks of brokers are for store and forward, not for HA of messages. i.e. a message only exists on one broker in a network at any point in time - its never HA across brokers > B) JDBC Master Slave Yes - the 3 master/slave alternatives are what you need http://activemq.apache.org/masterslave.html > BUT, what if broker dies before it writes its batch to the database, but > after it completes its fast-journal? It depends which of the 3 master/slave alternatives you are using - but with JDBC Master/Slave you don't use the journal -- James ------- http://radio.weblogs.com/0112098/