Hi Matt, thanks for the response.
The reason that we have not migrated to a later version of ActiveMq is that we are looking to move away from using ActiveMq due to the problems we have had. Therefore, we wanted to avoid going through the whole testing process for a later version of ActiveMq. We use shared nothing master/slave replicated which has been removed in later ActiveMq versions. We are doing JMS local (originally we tried XA but had massive problems with that) and we have tested with all caching settings for the DMLC to no avail. Our connection is not provided from a pool but directly from standard ActiveMq connection factory (org.apache.activemq.ActiveMQConnectionFactory), due to the fact that it is cached in the DMLC. Thanks, Justin -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-performance-problem-with-Tx-tp4685226p4685279.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
