Hi,

I've been running some load tests on a Spring Integration system backed by
ActiveMQ 5.2.0. I noticed that one of my application components was leaking
memory, and heap analysis showed this memory to be
org.apache.activemq.management statistics related. In particular, instances
of CountStatisticImpl and TimeStatisticImpl are being created at an alarming
rate, and they're not being garbage collected.

The pertinent behavior of Spring Integration
(DefaultMessageListenerContainer, for those who care) is that it creates a
fixed number of sessions on a single connection, and then a fixed number of
message consumers on those sessions. These sessions and consumers are kept
for the lifetime of the application. A message producer is created for each
outgoing message.

I have already disabled statistics on the broker (enableStatistics="false"),
but the problem persists. Is there any way to disable statistics on the
broker's clients?

Thanks,
Emerson
-- 
View this message in context: 
http://www.nabble.com/Possible-memory-leak-in-statistics-gathering-tp23572764p23572764.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to