Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 90063 invoked from network); 3 Jul 2009 03:49:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jul 2009 03:49:10 -0000 Received: (qmail 60788 invoked by uid 500); 3 Jul 2009 03:49:20 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 60636 invoked by uid 500); 3 Jul 2009 03:49:18 -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 60626 invoked by uid 99); 3 Jul 2009 03:49:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2009 03:49:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2009 03:49:07 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MMZlW-0001bL-Nd for users@activemq.apache.org; Thu, 02 Jul 2009 20:48:46 -0700 Message-ID: <24317212.post@talk.nabble.com> Date: Thu, 2 Jul 2009 20:48:46 -0700 (PDT) From: DCMH To: users@activemq.apache.org Subject: Re: Getting Durable Messages After Failover In-Reply-To: <24273253.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dmhcheng@gmail.com References: <24162563.post@talk.nabble.com> <24273253.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Thanks for answering. But my problem is that the 2 brokers are up and running, scenario as below: A B C broker 1 ----+-------- ------------- broker 2 ----+------ Client connects to broker 1 and consume message A and disconnected before unsubscription, message B is published before the client reconnects. Later the client reconnect to broker 2 using the failover protocol. However, it was unable to resume the session established in broker 1 so it cannot consume message B as it was delivered to broker 1. While the client is connecting to broker 2, message C is published and the client is able to consume message C. However, it seems that the session established in broker 1 is still valid and broker 1 still get message C. Later, the client get disconnected again and reconnects to broker 1 using the failover protocol, it gets message B and C from broker 1. There are 2 potential problems: 1) the client will not be able to get message B if it keeps connecting to broker 2 after the first reconnection. 2) the client gets a duplication of message C when it connects to broker 1 after the second reconnection. I have no idea on how to make use of the Replicated Message Stores in this case since both broker 1 and broker 2 are up and running at the same time (working in a cluster, instead of Master-Slave). Would you mind to explain in more details? Much appreciated for your help. You need to replicate the messages between the two brokers. See http://activemq.apache.org/clustering.html and look for "Master Slave" or "Replicated Message Stores" -- Open Source Integration http://fusesource.com -- View this message in context: http://www.nabble.com/Getting-Durable-Messages-After-Failover-tp24162563p24317212.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.