Hi,
Indeed PooledConnectionFactory is the way to go if you want to have the best
performances with ActiveMQ.
Can you tell us a little bit more on how you do send your messages to be so
badly impacted by the lock on the pool? I suppose your are using the
JmsTemplate from Spring to send your mes
Thanks. I did increase my session size to 100. So it cached sessions. The
problem was with Single connection Object. All the threads were trying to
use the same connection. Connection Object uses this Mutex before sending.
So essentially this is a blocker.
java.lang.Thread.State: BLOCKED
Hi,
By default, CachingConnectionFactory only caches a single session, as explained
on the JavaDoc of the class
(http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/jms/connection/CachingConnectionFactory.html):
"By default, only one single Session will be cached, with furt
