https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32558
--- Comment #21 from David Cook <dc...@prosentient.com.au> --- (In reply to Jonathan Druart from comment #14) > From > https://www.grzegorowski.com/rabbitmq-406-channel-closed-precondition-failed > > "You have to ACK messages in same order as they arrive to your system" > > If this is correct, forking is not an option here. Or rather, Kyle's patch is just forking at the wrong point. I've just reviewed the patches again, and I notice that this is a forking job server style, but we need a pre-forking job server style. That is, following GetOptions, we should fork, and each child process gets its own connection with RabbitMQ. Then each child process ACKs the messages in the same order it receives on its own separate connection (and channel). That way, it's functionally the same thing as running 4 separate background job worker processes. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/