I don’t recommend using the same pool for consumers (especially if you use local or XA transactions). The benefit is pretty minimal, and it can cause issues once you start scaling.
I don’t see pooling being a big boost for the number of total connections you are describing, but it might make configuration management easier. On Aug 13, 2014, at 1:00 AM, Sophia Wright <sophiawrigh...@gmail.com> wrote: > Hi, > > And how should I use pooledConnection factory. > Should I use different pooled ConenctionFactory for each listener and > producer > or should I use only one pooled connection factory with maxConnection to > required number. > > I can a see a similar thread > http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-for-durable-subscription-on-broker-restart-td4684381.html > > > > > > ~ Sophia > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-to-create-multiple-subscribers-and-producers-in-a-application-tp4684440p4684504.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
