activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From deepak_a <angesh...@gmail.com>
Subject Re: Query on activeMQ Queue's MemoryLimit (consumer getting blocked)
Date Mon, 11 Mar 2013 09:41:17 GMT
Thanks,

in addition, when there is an exception in my system, I store the message in
a DLQ and also persist the message in Database.

What I noticed is - 
* for every exception caught we were pushing the message to DeQueue
* the DeQueue also had a limit of 64MB
* if that limit got crossed , camel was not able to push any more messages
into my actual Queue 
* even after restarting I was seeing the memory being used to 100% in DLQ

I do persist the message to a Database, so I should not see the message in
the DLQ once it has been persisted, right?
(I may need to consider a few design change here)

If the messages are expected to be "retained" in the DLQ - there there is
every chance for the Queue size to fill up at some point in future, should
my system also be flexible enough for an automatic clean up of messages in
DLQ?



--
View this message in context: http://activemq.2283324.n4.nabble.com/Query-on-activeMQ-Queue-s-MemoryLimit-consumer-getting-blocked-tp4664495p4664596.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message