Reputation: 2068
i want to achieve that a message can only be consumed in 60 seconds. That way i have two Queues:
Gets consumed but never directly published.
Arguments:
Bound to exchange worker
(type = direct).
Gets published but never consumed.
Arguments:
Bound to exchange scheduler
(type = direct).
When i send a message to scheduler
it appears for 2 seconds, then disappears - as expected.
What i would expect next, is, that the message pops up in the worker
queue, but isn't appearing.
I'm not binding a routing key or anything else.
Question: Why don't expired messages get re-published in the dead letter exchange?
Upvotes: 0
Views: 1296
Reputation: 3509
Dead-Letter Exchange is an exchange, you need to bind the worker queue to the DLX with a suitable policy for the messages that are dead-lettered to land in the worker queue.
Upvotes: 1