[rabbitmq-discuss] Can't reject messages to DLX unless first published to an exchange

[Fredrik Sörensson (Fredrik Sorensson/STO/Fritidsresor)]

Hello.

I am looking at the RabbitMQ implementations in my organization, and right now how we handle errors. I made a very simple test in Perl using Net::AMQP::RabbitMQ to reject messages, to learn how it works.

I noticed that when I put a message directly to a queue which I then rejected, the message was not backed out to  the dead letter queue, it was just silently dropped. But if I posted a message to an exchange that was bound to my queue and then rejected that message, it was backed out to my dead letter queue. The dead letter exchange was configured using arguments to the queue.

So it seems a message can only be backed out to a dead letter exchange if it at one point in time has been published to an exchange. Is this the intended behavior? Or could it be an artefact of the Perl library I'm using?

/Fredrik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140519/ec95c537/attachment.html>