Thanks Reynald, that utility could be useful. I think I have already pinned down this problem to be opening and closing of connections to the broker. If I share a single or a couple of connections for all processing, I do not get the broker slowdown issue. Unfortunately, our application runs in GlassFish and without closing down the connections explicitly in the code after each request, the container cannot keep up with connection pool management and the pool is quickly exhausted. I still do not understand exactly what is causing the decline in broker performance over time when opening and closing connections to the broker for multiple concurrent requests.
-- View this message in context: http://activemq.2283324.n4.nabble.com/Slow-throughput-after-several-hundred-messages-tp3082431p3090649.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
