https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32573 --- Comment #6 from Kyle M Hall <kyle@bywatersolutions.com> ---
I can't see any scenario where either: A) We should ack before processing. We are stymying Koha's ability to do background processing by running extrememly long processes in serial with no way to fork multiple background jobs at one.
B) RabbitMQ/STOMP is the wrong tool for the job and we should remove it's use from Koha.
Actually, I can revise A a bit. We can fork and give the existing rabbit connection to the child process, and have the parent start a new connection to pass off again. That mains we can parallel process without acking first. It doesn't solve the 30 minutes time limit ( which is why I'm going to continue advocating for acking first ) but it does improve the situation greatly. -- You are receiving this mail because: You are watching all bug changes.