Hi Matt, we don't use JmsTemplate in this particular bit of code.
I have done some testing this morning and the problem seems to be contention with the shared connection. The Spring DMLC is configured to cache at Connection, Session and Consumer level. If caching is enabled at all (connection+) then it uses a shared single connection. I can verify this by monitoring ActiveMq through Jmx. So if I have a DMLC with 20 consumer threads, all sharing the same connection it is slow, but at low throughput you would not notice. If I create 20 separate DMLCs all with a single thread and all with different connections, then the performance is great in comparison! Not sure why this would be as I believed that it is normal to share the connection for JMS unlike JDBC and I would of assumed that ActiveMQ is optimised for that case? Thanks, Justin -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-performance-problem-with-Tx-tp4685226p4685365.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
