https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #249 from Julian Maurice <julian.maur...@biblibre.com> --- (In reply to Jonathan Druart from comment #247) > This last patch adds the ability to process the jobs even if the message > broker is not installed/configured correctly. > > I am not sure it is a good idea, we will want to make the message broker > mandatory at some point anyway (for messages not in the DB for instance). > And so we are only postponing the problem. 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 -- 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/
