I've been using RabbitMQ 3.8.9 on a Windows server for several months with no problems. We recently upgraded our server hardware and I did a completely fresh install of RMQ, upgrading to 3.8.17 in the process.
I have one long running process that used to run fine, but is now generating a "delivery acknowledgement timeout" error. I know I can increase this timeout in the config files, but I am trying to figure out why this process never threw these timeout errors when using 3.8.9.
Looking through the release notes, it looks like the timeout default was actually increased from 15 to 30 minutes in a recent release, which makes even less sense! The log message I am getting looks like this:
2021-06-28 13:41:22.310 [warning] <0.9987.0> Consumer amq.ctag-UiHtX6AUIwPD6stE8nh64g on channel 1 has timed out waiting for delivery acknowledgement. Timeout used: 1800000 ms. This timeout value can be configured, see consumers doc guide to learn more
2021-06-28 13:41:22.310 [error] <0.9987.0> Channel error on connection <0.9916.0> ([::1]:54147 -> [::1]:5672, vhost: '/', user: 'redacted'), channel 1:
operation none caused a channel exception precondition_failed: delivery acknowledgement on channel 1 timed out. Timeout value used: 1800000 ms. This timeout value can be configured, see consumers doc guide to learn more
2021-06-28 13:45:17.282 [warning] <0.9928.0> closing AMQP connection <0.9928.0> ([::1]:54151 -> [::1]:5672 - SecuritiesData.Service, vhost: '/', user: '
client unexpectedly closed TCP connection
Before I just increase the timeout and call it a day, I'd love to understand why this just started happening. Nothing has changed with my consumers or the processes that are sending messages over RMQ - in fact, if I point my programs to the old server, they run just fine.
Thanks in advance for any info you can provide!