Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 80858 invoked from network); 23 Feb 2010 18:02:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Feb 2010 18:02:32 -0000 Received: (qmail 16286 invoked by uid 500); 23 Feb 2010 18:02:32 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 16256 invoked by uid 500); 23 Feb 2010 18:02:32 -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 16246 invoked by uid 99); 23 Feb 2010 18:02:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 18:02:32 +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 (nike.apache.org: domain of jcarlson@e-dialog.com designates 208.94.20.29 as permitted sender) Received: from [208.94.20.29] (HELO corp-mail.e-dialog.com) (208.94.20.29) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 18:02:24 +0000 Received: from [10.65.4.0] (10.65.4.0) by eeyore.ad.e-dialog.com (10.100.8.45) with Microsoft SMTP Server id 8.2.234.1; Tue, 23 Feb 2010 13:02:03 -0500 Message-ID: <4B8417B9.4060701@e-dialog.com> Date: Tue, 23 Feb 2010 13:00:25 -0500 From: Josh Carlson Reply-To: jcarlson@e-dialog.com Organization: E-Dialog User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-3.fc11 Lightning/1.0pre Thunderbird/3.0 MIME-Version: 1.0 To: Subject: Message State persistence with failover Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I've been prototyping a 'shared file system master/slave' implementation. I'm using the Stomp protocol in my client and am trying to get failover to work properly. Currently when I failover to a new master, pending messages are persisted in the new master. However, message state seems to be lost. We use client acknowledgements and if I have a consumer that retrieves a message from the old master and then tries to acknowledge the message on the new master the ack appears to succeed but the message stays pending and winds up getting re-delivered. Is this scenario suppose to work? Any advice would be appreciated. Thanks Josh