Hello Fridolin,
Yes, performance is probably important for MQ, it seems to eat a
disproportionate amount of resources sometime. :)
But like I said, our server is a beast. In every aspect of its build,
it has the best components for 2022.
Let's see about the race condition:
* An update
1
Australia
Office: 02 9212 0899
Online: 02 8005 0595
*From:*Koha-devel
<mailto:koha-devel-boun...@lists.koha-community.org> *On Behalf
Of *Philippe Blouin
*Sent:* Wednesday, 21 December 2022 6:13 AM
*To:* koha-devel@lists.koha-community.org
*Subjec
t Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Koha-devel
> *On Behalf Of *Philippe
> Blouin
> *Sent:* Wednesday, 21 D
Hi,
I think network performance is really important for RabbitMQ.
We at Biblibre have a virtual machine in each server, to share between
each virtual machine (one Koha per machine) but keep a good network
performance.
Looks to work well, but we are still in 21.11.
Best regards,
Le
jup, the JSON bug hit us too
we also encountered some problems regarding rabbitmq/workers
debugging wasn't straigthforward because I had a hard time to find meaningful
debug output.
luckily the folks on IRC were very helpful as usual.
the latest bug (not sure if it is a bug as of yet) was
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
From: Koha-devel On Behalf Of
Philippe Blouin
Sent: Wednesday, 21 December 2022 6:13 AM
To: koha-devel@lists.koha-community.org
Subject: [Koha-devel] The many failings of background_jobs_worker.pl
Howdy!
Since
I've also been bitten by the malformed JSON string error.
On Tue, Dec 20, 2022 at 12:13 PM Philippe Blouin <
philippe.blo...@inlibro.com> wrote:
> Howdy!
>
> Since moving a lot of our users to 22.05.06, we've installed the worker
> everywhere. But the number of issues encountered is staggering.
Howdy!
Since moving a lot of our users to 22.05.06, we've installed the worker
everywhere. But the number of issues encountered is staggering.
The first one was
Can't call method "process" on an undefined value
where the id received from MQ was not found in the DB, and the process
is
