https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481 --- Comment #10 from David Cook <dcook@prosentient.com.au> --- (In reply to David Cook from comment #8)
(In reply to Katrin Fischer from comment #5)
A timeout seems arbitrary when you ultimately want all jobs to be processed and nothing be lost.
The RabbitMQ message broker doesn't know if the message was received by the consumer though. All it knows is that it sent a message. It doesn't know that it's being worked on.
I run a large IoT system and without timeouts you end up waiting for a response forever. 30 minutes is arbitrary but they make it configurable so that you can adjust it to your workload. Of course, in the case of Koha, we have less control over what people do with their RabbitMQ. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.