From users-return-12886-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Wed Feb 27 20:10:18 2008 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 24244 invoked from network); 27 Feb 2008 20:10:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2008 20:10:16 -0000 Received: (qmail 18440 invoked by uid 500); 27 Feb 2008 20:10:11 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 18419 invoked by uid 500); 27 Feb 2008 20:10:11 -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 18410 invoked by uid 99); 27 Feb 2008 20:10:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 12:10:11 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdixon@omniti.com designates 8.8.38.16 as permitted sender) Received: from [8.8.38.16] (HELO edge.omniti.com) (8.8.38.16) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 20:09:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=omniti.com; s=s1024; c=simple/simple; q=dns/txt; i=@omniti.com; t=1204142984; h=From:Subject:Date:To; bh=lZABCQR4wr8ntOqoJQZ7j0pYSe/B6iRa4LHepY9JQt8=; b=fQ+/CO7/SM/h8zHCLCYBmkXM/IwTmli6zv0toDvap1Wk1zSq5FBc2GZCSXW1La5g e7XOUaOHllKQKt52161AHHuwhAm8hOoFhD5F76RfNWCWTzp5iR8nwE81afgrW4kX nppN0yEF+mfZzvAPyeaC77v9IgQdnFRYlMPk/0dg2X4=; Authentication-Results: edge smtp.user=jdixon@omniti.com; auth=pass (PLAIN) Received: from [8.8.38.2] ([8.8.38.2:51076] helo=office-0-16.office.omniti.com) by edge (envelope-from ) (ecelerity 2.2.1.26 r(22409M)) with ESMTPSA (cipher=AES128-SHA) id 95/B9-10202-883C5C74; Wed, 27 Feb 2008 15:09:44 -0500 Message-Id: <25BE7DF2-47D4-4F9D-BAAA-66D0F4601368@omniti.com> From: Jason Dixon To: users@activemq.apache.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Subject: Synchronization of MasterSlave Date: Wed, 27 Feb 2008 15:09:42 -0500 X-Mailer: Apple Mail (2.919.2) X-Virus-Checked: Checked by ClamAV on apache.org We're testing ActiveMQ 5.1 with some php/stomp clients and java consumers. We noticed that messages consumed and deleted off the Master broker aren't purged off the Slave broker. When I first read the MasterSlave documentation, I read the following passage and assumed it to be referring only to the manual recovery process, given the context. But after seeing this behavior, I can't help but wonder if MasterSlave is "broken" in that it doesn't truly synchronize the Slave broker while the Master is still active. "There is no automatic synchronization between brokers. This is a manual process." Can someone clarify this behavior? Is there a way to enforce that deletions are on the Master broker are removed from the Slave as well? Thanks, --- Jason Dixon OmniTI Computer Consulting, Inc. jdixon@omniti.com 443.325.1357 x.241