[rabbitmq-discuss] RabbitMQ Dead Letter Routing

Tue Aug 21 10:59:21 BST 2012

You could bind your reply queue to the dead-letter exchange and you should
receive it back. Unfortunately, this approach does not distinguish 
producers
and as consequence of this sends also messages that did not refer only to
particular senders. You could get around this by using parts of routing 
keys
dependent on who sent the message in the first place.

Regards,
Ernest Staszuk

W dniu 2012-08-16 11:17, Paul pisze:
>
> Hello,
>
> I am hoping someone can help me out on this issue.
>
> I have got a typical setup of a async consumer, consuming from a 
> Queue, and a async producer (with a reply_to queue set) producing to 
> an exchange.
>
> I am facing the challenge of working with Dead Letter Queues and TTL.
>
> In a nutshell the producer needs a ways to determine if his/her 
> message ended up dead (in the event the consumer is too slow or not 
> "alive"). So this is what I have come up with but am struggling to 
> implement it (it might be impossible).
>
> Producer produces the message (with a reply_to property) -> Rabbit 
> Expires the message based on the TTL -> sends the message to a dead 
> letter exchange -> the exchange routes the message to the reply_to 
> queue property on that message -> the producer now consumers from that 
> queue (the reply_to queue).
>
> Question... "the exchange routes the message to the reply_to queue 
> property on that message"... is this possible and how?
>
> Any other suggestions on implementation or design which would meet my 
> criteria would be greatly appreciated.
>
> Thanks!
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120821/f5bace5c/attachment.htm>