https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 --- Comment #251 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to Julian Maurice from comment #249)
IMO we should not rely on the connection status (RabbitMQ is reachable or not) but instead on the configuration (RabbitMQ is configured or not). For instance, if configuration for RabbitMQ exists in $KOHA_CONF, use that, and if it is not reachable then die. And if there is no configuration, use the "dumb" worker system. That would allow people to just use the dumb system if it works for them, and if not sufficient they can "upgrade" by installing and configuring RabbitMQ
So far there is no configuration, the default parameters are used and hardcoded in the connection method. (In reply to Marcel de Rooy from comment #250)
If we feel that RabbitMQ is not ready for primary processes like the batch record modify in this patch set, we should remove that part. I would not promote a hybrid solution that falls back to code without MQ. It should just be stable enough to operate on and seen as an essential component.
I am against removing background jobs like batch record modify, it's the main point of this first step. -- You are receiving this mail because: You are watching all bug changes.