activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: Query around ActiveMQ.DLQ
Date Fri, 10 May 2013 13:33:03 GMT
When a message goes into a DLQ it means "the consumer cannot handle this
message for one reason or another" so it should be looked at. For your
usecase, if it's fine that messages can go undelivered and it's not a big
deal, you can just ignore the DLQ and use <discardingDLQBrokerPlugin> to
just drop everything that comes to DLQ. If you're interested in DLQ, but
just at certain times, and it's not necessary to know about all undelivered
messages, you can set TTL on messages so they eventually expire. And
lastly, if those messages in DLQ should be replayed or at least evaluated
for why they couldn't be delivered and you cannot lose any of them, then
use Camel to reroute them or put them into a database.

On Fri, May 10, 2013 at 2:59 AM, deepak_a <> wrote:

> Thanks Christian,
> On
> 'Maybe just write a camel route to put those messages into a database for
> future analysis? '
> - Will definitely consider that.
> Does this also mean - I am fundamentally 'not' using DLQ in Message-Broker
> for what they are actually meant for?
> i.e. is it always a bad idea to leave messages in Queues indefinitely?
> is there any recommendation/best-practice on how to use DLQ effectively?
> like setting a expirationTime?
> regards,
> D
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

*Christian Posta*
twitter: @christianposta

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message