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





Reply via email to