Justin-
JMS connections act and behave very different from JDBC connections. Just like
a long query can block other apps trying to access the connection on a shared
JDBC connection, a slow consumer can impact others trying to access it as well.
You can do multiple sessions on top of a single c
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+)
Justin-
Sorry to hear that you’ve had problems with ActiveMQ in the past. I’ve had a
lot of successful deployments in large-scale environments (3,000+ brokers, hub
and spoke with 1 broker serving up to 1,000 clients, 4,000 queues and 3,000
total connections) with transactions, and the full boat
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. W
Hi James-
ActiveMQ 5.5.1 is quite aged at this point. Any reason you aren’t looking at a
newer version?
Transactions and connection pooling is tricky— are you doing XA or JMS Local?
I suggest trying to get it all working, then tune.. CACHE_NONE first.
-Matt
On Sep 2, 2014, at 7:05 AM, James
