https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32393
--- Comment #20 from Jonathan Druart <[email protected]> --- (In reply to Marcel de Rooy from comment #19) > (In reply to Kyle M Hall from comment #9) > > Just a thought; removing that fork will cause the workers memory footprint > > to balloon as soon as the plugins require is evaluated which obviates the > > bug patch where you introduce the require. I think this pushes us farther in > > the direction of needing to ack each request before handling the job. > > Looks like there is consensus on keeping the fork. The problem does not seem > to be related to forking. > Did you consider moving the ->ack before the process start as Kyle > suggested? It is simpler than the current code with finally. And it is still > possible to run the worker without rabbitmq to recover if really needed? See bug 32573. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] 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/
