[rabbitmq-discuss] Dead letter exchange behavior / best practice
watson.timothy at gmail.com
Mon Oct 29 08:25:08 GMT 2012
On 28 Oct 2012, at 07:53, Ludovic Fleury <ludo.fleury at gmail.com> wrote:
> I tried another setup which seems to don't work either...
> So I assume cyclic DLX are not allowed ?
Correct, although we're considering dropping this restriction in a future release.
> Le dimanche 28 octobre 2012 07:41:54 UTC+1, Ludovic Fleury a écrit :
> I'm new to RabbitMQ and I try to use the dead letter exchange feature.
> Yet, I don't know if I make a misstake or if I misunderstand the documentation about it:
> As far as I read in the doc:
> The dead-lettering process adds an array to the header of each dead-lettered message named x-death.
> This array contains an entry for each time the message was dead-lettered.
> Each such entry is a table that consists of several fields
> So basically, I have 2 queues and 2 exchanges:
> -"my-exchange" bound to "my-queue"
> -"my-dead-exchange" bound to "my-dead-queue"
> I have set a DLX on "my-queue" to "my-dead-exchange" and I have set another DLX on "my-dead-queue" to ... "my-dead-exchange".
> The last DLX is a cylic DLX. I hope this is okay ?
> When I first reject a message on "my queue", everything is okay: I have the message handled by "my-dead-exchange" and placed to "my-dead-queue".
> But then, when I reject again the message... The message is not handled by "my-dead-exchange" and nor replaced into the "my-dead-queue".
> With the documentation, I understand that: every time a message is rejecteted, I would be able to "count" the number of rejection by counting on the "x-death" header.
> So instead of rejecting with a requeue, I would like to take advantage of this behavior by rejecting into a "cylic DLX" (to count the total of rejection for a message).
> Is my implementation incorrect ? How can I handle this need in RabbitMQ ?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss