Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 33719 invoked from network); 20 Sep 2007 03:11:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Sep 2007 03:11:30 -0000 Received: (qmail 18071 invoked by uid 500); 20 Sep 2007 03:11:21 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 18043 invoked by uid 500); 20 Sep 2007 03:11:21 -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 18034 invoked by uid 99); 20 Sep 2007 03:11:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 20:11:21 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG 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; Thu, 20 Sep 2007 03:11:20 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IYCRP-0000sO-UL for users@activemq.apache.org; Wed, 19 Sep 2007 20:10:59 -0700 Message-ID: <12790117.post@talk.nabble.com> Date: Wed, 19 Sep 2007 20:10:59 -0700 (PDT) From: tendlu To: users@activemq.apache.org Subject: Equivalent of Tibco EMS FailSafe MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: surajn@yahoo-inc.com X-Virus-Checked: Checked by ClamAV on apache.org Tibco has a configuration to mark a queue "fail safe". This means the messages for a "fail safe" queue is synchronously written to the disk. In other words, no buffering is done for write (probably uses fsync -- that gaurantees the data is flushed to the disk). If the server goes down, no message is lost. This is described as the most "reliable mode". Is there an equivalent to this in ActiveMQ? Tibco also has a "non fail safe" mode for the queues which means it does not synchronously write to the disk. On other words, some kind of buffering is done by the writer. "Non fail safe" mode performs far better than "fail safe" because of the synchronous write. thanks in advance. -- View this message in context: http://www.nabble.com/Equivalent-of-Tibco-EMS-FailSafe-tf4485108s2354.html#a12790117 Sent from the ActiveMQ - User mailing list archive at Nabble.com.