Hi, You seem to be mixing concerns in your message. Connection Pooling has nothing to do with Load Balancing.
Connection Pooling is a way to prevent constant recycling of connection objects and thereby gaining performance and capacity in dealing with high message throughput. Load Balancing is entirely separate. The Broker simply dispatches messages on a connection that has capacity available in the consumer prefetch against a given consumer using the connection. The broker can be directed to spread the load (aka load balance) using a broker dispatch policy ( http://activemq.apache.org/dispatch-policies.html http://activemq.apache.org/dispatch-policies.html ) which is configured on the broker not on a camel route consumer that uses an pooled ActiveMQ connection factory. Hope this helps. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com CamelOne 2011: http://fusesource.com/camel2011 --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/Answer-multiplication-ConnectionPooling-Whats-that-for-tp4541717p4542112.html Sent from the Camel - Users mailing list archive at Nabble.com.
