Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3072111B34 for ; Mon, 5 May 2014 02:41:25 +0000 (UTC) Received: (qmail 7114 invoked by uid 500); 5 May 2014 02:41:24 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 6620 invoked by uid 500); 5 May 2014 02:41:23 -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 6612 invoked by uid 99); 5 May 2014 02:41:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2014 02:41:22 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of iamleejt@gmail.com does not designate 216.139.250.139 as permitted sender) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2014 02:41:18 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Wh8pS-0003PX-9e for users@activemq.apache.org; Sun, 04 May 2014 19:40:30 -0700 Date: Sun, 4 May 2014 19:40:15 -0700 (PDT) From: Charels_Li To: users@activemq.apache.org Message-ID: <1399257615279-4680841.post@n4.nabble.com> In-Reply-To: <1398971673208-4680788.post@n4.nabble.com> References: <1398327873281-4680504.post@n4.nabble.com> <1398841541745-4680732.post@n4.nabble.com> <1398971673208-4680788.post@n4.nabble.com> Subject: Re: delay failover transfer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The network of my firm was built a couple of years ago, whose bandwidth is limited. We are afraid there could be some lag/jam in data transmission. Say, a client losses contact with the broker due to an occasional network lag, but the connection could come to life after 2/3 seconds. In this case, we dont like the client switch forward/ backward for it could create some delay and message loss. Shall i use failover transport? Or there's some sophisticated configs i could try? -- View this message in context: http://activemq.2283324.n4.nabble.com/delay-failover-transfer-tp4680504p4680841.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.