Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 85843 invoked from network); 10 Mar 2009 09:17:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Mar 2009 09:17:44 -0000 Received: (qmail 37785 invoked by uid 500); 10 Mar 2009 09:17:43 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 37758 invoked by uid 500); 10 Mar 2009 09:17:43 -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 37747 invoked by uid 99); 10 Mar 2009 09:17:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2009 02:17:43 -0700 X-ASF-Spam-Status: No, hits=3.7 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_HOTMAIL_RCVD2,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; Tue, 10 Mar 2009 09:17:36 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Lgy5L-0005IY-IY for users@activemq.apache.org; Tue, 10 Mar 2009 02:17:15 -0700 Message-ID: <22430481.post@talk.nabble.com> Date: Tue, 10 Mar 2009 02:17:15 -0700 (PDT) From: centis To: users@activemq.apache.org Subject: Client side queue... MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: centis_biks@hotmail.com X-Virus-Checked: Checked by ClamAV on apache.org What happens when asyncSend is enabled and the broker has gone down or is unreachable. A collegue said that he read somewhere there is a "client side queue", some kind of local store that will cause the messages to be resent later when the broker recovers. Is there any such facility? The basic problem is that we can't have send block, but want persistence too. Thanks!! CB -- View this message in context: http://www.nabble.com/Client-side-queue...-tp22430481p22430481.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.