activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier OTTAVI" <>
Subject Re: PooledConnectionFactory - Spring - Loadbalancing in a network
Date Thu, 06 Sep 2007 16:22:41 GMT
That will result in easier connection managment between the nodes of the
network and even load of each brokers. I would like to be able to scale the
network of brokers without scaling automatically the producers. Like 2
producers and 3 brokers etc. Is Iona recommand architecture where load
balancing is done by assigning producers with specific broker ? Beside
thanks for the information on the average load that a broker can assume.

On 9/6/07, James Strachan <> wrote:
> On 9/6/07, Olivier OTTAVI <> wrote:
> > It seems from my perspective that the PooledConnectionFactory is caching
> > only one connection to the network. Since load balancing between nodes
> is
> > done at connection time, using PooledConnectionFactory will not work
> with
> > load balancing. Will this be a problem to have a real pool of jms
> > connections ? to preserve load balancing, and use pooling which reduce
> the
> > process of producing messages by a factor 10.
> Just out of interest; why are you trying to load balance JMS requests
> across JMS brokers for a single JVM? (which generally breaks ordering
> of queues)?. Why not have each JVM connect to one broker?  Test load
> balancing with multiple client JVMs?
> FWIW a single broker can usually handle a few thousand client JVMs; so
> the idea of one JVM talking to multiple brokers does seen a tad odd?
> Are you sure you're not confusing load balancing of consumers with
> that of having mutliple brokers?
> --
> James
> -------

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message