https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43729 --- Comment #12 from Tomás Cohen Arazi (tcohen) <tomascohen@gmail.com> --- Created attachment 207325 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207325&action=edit Bug 43729: Remove STOMP support from the background jobs worker RabbitMQ/STOMP is being retired in favour of SQL polling (see bug 42077, which already made polling the default and RabbitMQ optional). This patch removes the STOMP code path from the generic background jobs worker. Koha::BackgroundJob no longer connects to a message broker: the connect() method and the Net::Stomp enqueue path (send_with_receipt) are dropped. enqueue() now simply stores the job with status 'new' for a worker to pick up by polling. The process($args) contract is unchanged, so job classes keep receiving their decoded arguments. The worker loop is centralised into a new Koha::Worker class, so misc/workers/background_jobs_worker.pl becomes a thin wrapper that builds a Koha::Worker and calls run(). Koha::Worker polls for 'new' jobs in the requested queues, forks via Parallel::ForkManager, decodes each job's data and passes it to the job's process method. Test plan: 1. Apply patch 2. Run: $ ktd --shell k$ prove t/db_dependent/Koha/BackgroundJob.t \ t/db_dependent/Koha/BackgroundJobs.t \ t/db_dependent/Koha/BackgroundJob/ => SUCCESS: Tests pass! 3. Set up an instance without RabbitMQ, run the worker and trigger a background job (e.g. batch item modification); confirm it reaches 'finished' with no broker connection warnings in the logs. => SUCCESS: Job processed, no warnings! 4. Sign off :-D -- You are receiving this mail because: You are watching all bug changes.