On 24/12/2007, hagai <[EMAIL PROTECTED]> wrote: > > Hi, > I have some questions about load balancing: > We have a few server farms, and also multiple JMS clients deployed over the > internet. Computers in server farms can talk JMS to each other, and there is > also low volume communication between server farms. > The remote clients connect to the broker using SSL. HA is probably not > important to us. > > I want to use load balancing using a standard IP load balancer (such as > cisco ACE). I plan to provide two URIs for each server farm: One SSL URI for > the remote clients, and one TCP URI which will be used for communication > between server farms (over a VPN connection). I don't want to use load > balancing in the client using since I want to be able to add and remove > brokers without changing the clients. Therefore, the URIs will contain the > load balancer's IP. The client's URI will be something like > "failover:(ssl://lb.liveperson.net)". > > When a client, or broker from another server farm, connects the load > balancer it will select a broker, and all communication from this client > will reach the same broker until it is down. > > My questions are: > 1. Does this configuration make sense? :)
Sure. The combination of your IP load balancer and client side failover transport should work well. > 2. Is there a way to use multicast to send messages between brokers? since I > may have distributed topics and queues I want to be able to send messages > once for the whole server farm, and not duplicate it for each broker. Multicast isn't generally recommended for heavy duty messaging as the reliability layer is not too hot right now and multicast can often be disabled between hosts on different routers etc. We tend to recommend using TCP for messaging - and just using multicast for discovery. But feel free to experiment with it if you want; the worry is if your multicast buffer overflows you loose packets which could mean you loose messages. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
