Confirming Deliveries with Spring AMQP

Question

We're using Spring AMQP in the style of Spring Remoting with AMQP. I'm setting x-message-ttl on every message so that it expires immediately if it cannot be delivered immediately to a consumer. This works great, however, it leaves the producer waiting for the specified value of replyTimeout before failing with RemoteProxyFailureException (if I recall correctly). Is there any way I can make the producer fail immeditely if the message cannot be delivered (only waiting for the timeout if the message is actually received)?

Answer 1

The loose coupling of the architecture means there's no indication to the producer of the expiry.

There used to be an immediate flag but it was removed in rabbitmq 3.0.

On possible solution would be to configure a DLX/DLQ so the expired message can be consumed by another consumer, which can return an exception to the client.

EDIT:

Simply have the fallback consumer implement the same interface and have it throw an exception.

See this updated test case.