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.
