0

We updated RabbitMQ from 3.8.8 to 3.9.21 last week, and we are seeing issues with this error for existing applications:

Basic ack failed because channel was closed with message '"Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=406, text=\"PRECONDITION_FAILED - delivery acknowledgement on channel 3 timed out. Timeout value used: 1800000 ms

Looking at the application, we are running, it seems to be working fine, but only for 30 min, which I suspect to coincide with the timeout.

The application consumes data via EasyNetQ using _bus.Advanced.Consume<T>(queue, (msg, info) => callback(msg.Body)) from a fanout exchange and the stats are not indicating that messages are not ack'ed: enter image description here

Anyone has a clue about what is going on?

Mikkel LP
  • 71
  • 6
  • Does this answer your question? [how to increase Delivery acknowledgment timeouts rabbitMQ version is 3.10.1](https://stackoverflow.com/questions/72283638/how-to-increase-delivery-acknowledgment-timeouts-rabbitmq-version-is-3-10-1) – Bernd Linde Jul 05 '23 at 13:26

0 Answers0