activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jp <joseph.pac...@gmail.com>
Subject OutOfMemory in messageConsumer thread: activemq running out of memory
Date Fri, 09 Dec 2011 08:36:59 GMT
Hi

We're using a pattern where we keep a connection/session/message consumer
per thread. However, it happens sometimes that some threads go wild and fire
OutOfMemoryError. After that, memory usage starts to grow in activemq and
after some while (depending on the limit and the number of messages sent in
between), the memory limit is reached and activemq stops accepting messages. 

Currently, we then have to restart activemq, but the whole situation is
pretty poor.

While we're trying to resolve this issue at its root, we were also wondering
if there was some way to make sure activemq doesn't end up eating all its
memory. For example could we define a "time to live" for message consumer?
Or a timeout on the queue regarding the last read message (after what the
queue would drop the consumer assuming this one is dead)?

Thanks in advance for your help
best
joseph

--
View this message in context: http://activemq.2283324.n4.nabble.com/OutOfMemory-in-messageConsumer-thread-activemq-running-out-of-memory-tp4175801p4175801.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message