Rabbit MQ Recovery connection/channel/consumer with DLX failed

[Julien MARTIN]

Hello

I have 2 queues, I have enabled the AutomaticRecoveryEnabled parameter set to true to allow automatic reconnection in my application.

QueueTest is the main queue that receives messages.
QueueTestRetry is the DLX queue that receives messages that the consumer cannot process, for example, during an application exception.
However, it does not work when I specify the x-dead-letter-exchange parameters. Here is the error in the logs:

operation queue.declare caused a channel exception precondition_failed: inequivalent arg 'x-dead-letter-exchange' for queue 'QueueTestRetry' in vhost '/': received none but current is the value 'tdi.retry.exchange' of type 'longstr'

The configuration of my queues is as follows:

QueueTest contains the following parameters:

x-queue-type: quorum
x-max-in-memory-length: 50
x-dead-letter-exchange: tdi.wait.exchange
x-dead-letter-routing-key: QueueTest
QueueTestRetry contains the following parameters:

x-queue-type: quorum
x-max-in-memory-length: 50
x-dead-letter-exchange: tdi.retry.exchange
x-dead-letter-routing-key: QueueTest
However, if I do not specify the x-dead-letter-exchange and x-dead-letter-routing-key parameters, the reconnection works without error.

Is the AutomaticRecoveryEnabled parameter limited when using DLX?

I'm using RabbitMQ 3.11.11

[Luke Bakken]

Hello,

Thanks for using RabbitMQ. Please see the community support policy here - https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md#who-is-eligible-for-community-support

If you would like us to assist you, please do the following:

• Use the latest version of RabbitMQ, 3.13.x
• Provide a complete program that we can compile and run to see this issue. Right now you haven't even told us which client library you are using (Java? .NET?)
• Provide instructions for reproducing the issue.

Luke

Team RabbitMQ

[Julien MARTIN]

Hello

This is a complete program :  https://github.com/exile69000/RabbitMQApp.git

I'm using .NET library.

For reproducing the issue, pull rabbitmq:3-management image docker.

Run container : docker run -it --rm -p 15672:15672 -p 5672:5672 rabbitmq:3-management

Compile and execute the program. When you see a consumer on queue "QueueTest", go to Connections menu, click on the connection and close it.

Then in container log, we can see : 

[Luke Bakken]

Thank you, I can reproduce this issue and am investigating. It is very helpful to have code!

[Luke Bakken]

Hello,

Your issue is this code:

https://github.com/exile69000/RabbitMQApp/blob/master/RabbitMqDlx/Program.cs#L64-L65

The .NET library does not make a copy or deep clone of the arguments dictionary, so you're actually changing the arguments for when recovery happens. Don't do that. I will make sure that a clone is done in version 7 of the library.

[Luke Bakken]

https://github.com/rabbitmq/rabbitmq-dotnet-client/pull/1616

I will make a chore to back-port this to the 6.x branch. Feel free to do that yourself if you'd like, and open a pull request against 6.x.

[Luke Bakken]

https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/1617

[Julien MARTIN]

Thank you,  Do you know when the next release will be published?

[Luke Bakken]

No, not really. I have to review what is going into version 6.9.0.

Since there is a workaround for this issue, it doesn't seem to be high priority.

Thanks for submitting that pull request, by the way.