Return-Path: 
 <activemq-users-return-4484-apmail-geronimo-activemq-users-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org
Received: (qmail 11953 invoked from network); 12 Sep 2006 23:57:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 12 Sep 2006 23:57:14 -0000
Received: (qmail 82169 invoked by uid 500); 12 Sep 2006 23:57:14 -0000
Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org
Received: (qmail 81976 invoked by uid 500); 12 Sep 2006 23:57:14 -0000
Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:activemq-users-help@geronimo.apache.org>
List-Unsubscribe: <mailto:activemq-users-unsubscribe@geronimo.apache.org>
List-Post: <mailto:activemq-users@geronimo.apache.org>
List-Id: <activemq-users.geronimo.apache.org>
Reply-To: activemq-users@geronimo.apache.org
Delivered-To: mailing list activemq-users@geronimo.apache.org
Received: (qmail 81966 invoked by uid 99); 12 Sep 2006 23:57:14 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from [64.14.253.182] (HELO mail.exist.com) (64.14.253.182)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Sep 2006 16:57:08 -0700
Received: from [192.168.241.120] ([58.71.14.245])
	(authenticated bits=0)
	by mail.exist.com (8.12.11/8.12.11) with ESMTP id k8CNpOU4032652
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <activemq-users@geronimo.apache.org>; Tue, 12 Sep 2006 16:51:28 -0700
Message-ID: <45074939.6090108@exist.com>
Date: Wed, 13 Sep 2006 07:56:41 +0800
From: Adrian Co <aco@exist.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: activemq-users@geronimo.apache.org
Subject: Re: Load Balancing with Single Consumer
References: <6247294.post@talk.nabble.com> <45060B5E.3000107@exist.com>
 <6259485.post@talk.nabble.com> <45064BC4.50001@exist.com>
 <6263142.post@talk.nabble.com>
In-Reply-To: <6263142.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

What do you mean it didn't work? Did you get any exceptions?

Could you post the broker and client output/logs?

apinke wrote:
> I did try setting up Multicast as mentioned in this post :
> http://www.nabble.com/broker-discovery-client-help-tf1651573.html#a4474136
>
> but the brokers just sat there and the producer did not send any messages at
> all !
>
>
> Broker X:
> <transportConnector uri="tcp://localhost:61616"
> discoveryUri="multicast://foo"/> 
> and network connector is: 
> <networkConnector uri="multicast://foo"> 
>
> Broker Y:
> <transportConnector uri="tcp://localhost:61617"
> discoveryUri="multicast://foo"/> 
> and network connector is: 
> <networkConnector uri="multicast://foo"> 
>
> The producer used the uri : 
> discovery:multicast://foo
>
> It didnt work. Anything wrong in the config ?
>
> Thanks
> Pat
>
>
>
> Adrian Co wrote:
>   
>> Do you mean having a multicast group of brokers?
>> http://www.activemq.org/site/multicast-transport-reference.html
>>
>> apinke wrote:
>>     
>>> Thanks Adrian..
>>>
>>> We already went through these and did manage to set up a network..the
>>> problem was
>>> 1) the other broker was used only when there was a failover and not as a
>>> load balancer
>>> 2) the other broker needed its own set of consumers.
>>>
>>> What we wanted to try out was if the 2 brokers would load balance but
>>> there
>>> would be only 1 consumer..
>>>
>>> thanks
>>> Pat
>>>
>>>
>>> Adrian Co wrote:
>>>   
>>>       
>>>> Wonder if these is what you are looking for:
>>>> http://www.activemq.org/site/networks-of-brokers.html
>>>> http://www.activemq.org/site/failover-transport-reference.html
>>>> http://www.activemq.org/site/masterslave.html
>>>>
>>>> apinke wrote:
>>>>     
>>>>         
>>>>> We are trying to achieve load balancing with single producer and single
>>>>> consumer instance and multiple Brokers.
>>>>>
>>>>> What we are trying to achive is have only one Consumer connect to one
>>>>> broker
>>>>> and listen to a queue but for load-balancing reasons ( or if the broker
>>>>> goes
>>>>> down ) ,  it should automatically connect to the next broker and
>>>>> consume
>>>>> the
>>>>> messages. 
>>>>> Is this setup possible ?
>>>>>
>>>>> To be more clear, can we create a "virtual" broker / queue that a
>>>>> producer
>>>>> and consumer can use , but it is actually composed of a network of
>>>>> brokers ,
>>>>> such that 
>>>>> they can share the load or provide failover capabilities.
>>>>> Of course , this is not load balancing the application but only the
>>>>> brokers...
>>>>>
>>>>> thanks
>>>>> Pat
>>>>>
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>>     
>>>>         
>>>   
>>>       
>>
>>     
>
>