In general, you should use the PooledConnectionFactory. The connections are created upfront which saves time. The connections are also reused which is more resource friendly.
Best, Christian ----------------- Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Tue, Oct 29, 2013 at 12:10 PM, Dayakar <daya.kond...@gmail.com> wrote: > Hi, > > Previously we are using ActiveMQConnectionFactory alone, and we observed > that while starting the JBoss Server ActiveMQ is creating multiple threads > and closing (ActiveMQ Task 1, ActiveMQ Task 2, ...), we thought it creating > multiple connections/session are creating and closing. > > As a resolution, we want to use PooledConnectionFactory > > 1) We are using Camel Routes to prepare and send messages to destination, > we > invoke 7 routes and each route configured with parallel processing (Min > value is 5 and max value is 25 threads), daily we process around 3 Lakh > Messages (= 300.000) and All Routes are TRANSACTED. > > In Parallel Processing Is it better to use PooledConnectionFactory? > > For Each Message PooledConnectionFactory create one session (or) Session > object will be shared by Multiple messages? > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Is-it-better-to-use-PooledConnectionFactory-in-Parallel-Processing-tp5742350.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
