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 further requested Sessions being created and disposed on demand. Consider raising the "sessionCacheSize" value in case of a high-concurrency environment." So you should consider increasing the session cache size to see if it help. Cheers, Reynald On Wednesday, April 13, 2011 at 4:51 , ks wrote: > I used Spring's CachingConnectionFactory and found that it uses only one > connection. When we run performance tests, threads are blocked to send > message ( even when it is async). > > So I tried using PooledConnectionFactory. Now threads are blocked more time > for getting connection ( creating the connection and also acquiring the > connection). With the pooling I would expect only first set of requests to > take time. But here it also took more time to get the created connection. > > > > > > > > Any suggestions? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/PooledConnections-Poor-Performance-tp3446142p3446142.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
