[rabbitmq-discuss] Dead Letter Channel?
james.r.carr at gmail.com
Fri May 27 21:45:58 BST 2011
So is there a good way to handle clients that can't understand a
message they recieve? Ideally this is more of a programmer mistake
rather than application behavior and should be handled by the teams
that maintain that code but just curious if there is a good abstract
way to store that message for later processing.
On Fri, May 27, 2011 at 3:37 PM, Matthias Radestock
<matthias at rabbitmq.com> wrote:
> James Carr wrote:
>> For now would an appropriate way to handle this be to just attach a
>> ReturnListener on each publisher and have those publish to a
>> designated "dead letter" queue?
> No, since returns are triggered by unroutable *publishes* and have nothing
> to do with *consumers* rejecting messages / dying when processing them.
> PS: next time, please mail the list.
More information about the rabbitmq-discuss