Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 76850 invoked from network); 2 Nov 2009 11:08:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Nov 2009 11:08:13 -0000 Received: (qmail 11587 invoked by uid 500); 2 Nov 2009 11:08:13 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 11532 invoked by uid 500); 2 Nov 2009 11:08:12 -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 11522 invoked by uid 99); 2 Nov 2009 11:08:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Nov 2009 11:08:12 +0000 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 gary.tully@gmail.com designates 209.85.218.215 as permitted sender) Received: from [209.85.218.215] (HELO mail-bw0-f215.google.com) (209.85.218.215) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Nov 2009 11:08:01 +0000 Received: by bwz7 with SMTP id 7so6691843bwz.6 for ; Mon, 02 Nov 2009 03:07:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=eqf8Q51b1m8Ak1BtY9lRqH9NRanS4hgFTXy+7XDE2yo=; b=c/C0wBe1ygOZC/AaSib2CgiboM+BDk8rymNG6lW+Lggy8LG/mrbK5mV6S8knvG3hZT B+YU5yG9R8PIuLXTt3gtj8EFzjDyI04AvKlKbQfdYCRktfX1ZdEq0BNWpD6eabdw2ESL 9flSr0mmDKHEUIKa4rXhH6DFy6jIz3E+N2RJ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=aANoycWAOHa+d3CdRIhAJB5H8AN8p45KVetS69sJ0xH/URGay+jNE26RC5kfkOdPlb OWvTVryDEeu1+YozbO6u79vqkE7w04HuLbN/jvXabjPjm4eK/uIIXoUE3lwGQVuBvSv6 o80rfvkQR9rz73E+zPiUZcTO9J1cW8XoFATlo= MIME-Version: 1.0 Received: by 10.204.13.201 with SMTP id d9mr3837173bka.12.1257160061286; Mon, 02 Nov 2009 03:07:41 -0800 (PST) In-Reply-To: <26156637.post@talk.nabble.com> References: <26156637.post@talk.nabble.com> Date: Mon, 2 Nov 2009 11:07:41 +0000 Message-ID: <3a73c17c0911020307r724bcf08xf1ac30dda7d20e8e@mail.gmail.com> Subject: Re: Queue Consumer and Failover setup From: Gary Tully To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org The failover transport uses the URI list when asked to make a new connection, so your publisher must be using a new connection for each send but your consumer must be maintaining a single long lived connection (which is no bad thing). If you want your consumer to round robin between both brokers then you need to have it close it's connection when it has consumed it's batch quota. 2009/11/2 devylon : > > Hi, > > i have setup my publishers to a queue with a failover connection > failover:(tcp://host1:61616,tcp://host2:61616)?randomize=true > > in the monitoring and logfiles i can see how the messages are published > either > to host1 or host2. > > For the consumer i'm using the same failover connection. BUT what i see > is that the consumer is only connecting to one of the brokers, e.g. host1. > All messages sent to host2 are pending in the queue. > > How can i configure the consumer to connect to both brokers and consume both > queues ? > > -- Ingo > > -- > View this message in context: http://old.nabble.com/Queue-Consumer-and-Failover-setup-tp26156637p26156637.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com