[rabbitmq-discuss] Transactions & Routing

[Jason J. W. Williams]

> Transactions and the new 'confirms' let the producer know that the broker
> has take responsibility for the message. It is perfectly ok for a message
> not to go anywhere during routing and thus be dropped. Indeed, leaving
> transactions and confirms aside, what is supposed to happen to persistent
> messages which do not get routed to any queues? Should the broker hold on to
> them in the hope that some queue will turn up eventually?

No, but since the client is synchronously waiting for the transaction
to return, it doesn't seem unreasonable for the transaction to fail if
Rabbit has to blackhole the message because there were no queues to
give it to.

-J