https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43729 --- Comment #1 from Tomás Cohen Arazi (tcohen) <tomascohen@gmail.com> --- Created attachment 207314 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207314&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. Set up a Koha instance without RabbitMQ. 2. Run misc/workers/background_jobs_worker.pl --queue default --queue long_tasks 3. Trigger a background job (e.g. batch item modification). 4. Confirm the job is processed and reaches 'finished', with no broker connection warnings in the logs. -- You are receiving this mail because: You are watching all bug changes.