[Koha-bugs] [Bug 33044] BackgroundJob enqueue does not return the job id if rabbit is unreachable

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33044

--- Comment #8 from Nick Clemens <nick at bywatersolutions.com> ---
(In reply to David Cook from comment #7)
> (In reply to Marcel de Rooy from comment #5)
> Imho, we should focus on it just working with rabbitmq.
>

I agree, Rabbit should be the focus, but as long as this code is still there,
we should make it work :-)

> > Should we put more time in getting it stable in Koha? Is the plugin we use
> > the cause of that? Bad configuration? Many people run it and it should be
> > able to handle millions of messages.. The volume of messages in Koha is not
> > expected to be that large. I'm curious about this as well. I use RabbitMQ for a different system and I process hundreds of thousands of messages a day (usually in bursts of several per second) with zero problems. 

I think we are much closer - with the initial implementation we had may
problems in production (connection failing, jobs being lost, things getting
'stuck') so we went back to using the DB polling

> I do use the AMQP for that one instead of the STOMP but I'm not sure what
> people's problem with RabbitMQ is...

Our goal is to run rabbit in production, and we are working on moving all the
bugs to address our issues forward too. We are waiting for the next stable
release, and then will begin switching back and seeing how things go

-- 
You are receiving this mail because:
You are watching all bug changes.