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 15:37:36 GMT
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.

On 9/5/07, Olivier OTTAVI <> wrote:
> Dear all,
>  I am trying to use the PooledConnectionFactory with Spring on a producer
> connected to a network of brokers (B1 and B2).
>  The scenario is the following : I start B1 and B2 and send 100 messages
> to the network with the brokerURL : failover:(tcp://myip:61616,
> tcp://myip:62626) .
>  Then I stop one of the broker, and start three receivers on the same
> destination queue.
>  In the case I did not use the PooledConnectionFactory, the receivers get
> only the messages that went to the broker still alive in the network,
>  but when I use PooledConnectionFactory, depending on the broker I
> stopped, I get all the messages or none of them, so I think in this case,
> load balancing, is not properly processing when the message are dispatched.
> Any advice on the configuration of a dispatcher with spring.

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