https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30410
--- Comment #18 from David Cook ---
Do we have any examples of this one?
--
You are receiving this mail because:
You are watching all bug changes.
___
Koha-bugs mailing list
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32558
--- Comment #23 from David Cook ---
(In reply to Kyle M Hall from comment #10)
> Would that work with the database polling method? I think that would require
> some re-engineering.
Upon review, that won't work with having multiple
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32558
--- Comment #22 from David Cook ---
Was tempted to Fail QA this one, but I haven't actually tested if the current
patch won't work in practice.
But I think moving the forking up as I describe above would be a wise move.
--
You
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #33 from David Cook ---
That 3rd patch "Bug 32481: Use correct prefetch syntax for RabbitMQ" uses the
correct syntax, so the worker only fetches 1 message at a time ( see
https://www.rabbitmq.com/stomp.html#pear.p )
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #32 from David Cook ---
(In reply to Jonathan Druart from comment #25)
> I am giving up, need help.
I am terribly sorry for wasting your time on this one, Jonathan.
I solved this problem on a different project using
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #31 from David Cook ---
Created attachment 145134
-->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=145134=edit
Bug 32481: Use correct prefetch syntax for RabbitMQ
According to
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #30 from David Cook ---
I'm thinking that the prefetch config I provided isn't working with
Net::Stomp...
I enqueue 100 messages and then I look at the channel.
root@kohadevbox:kohadevbox$ rabbitmqctl list_channels
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #29 from David Cook ---
Ok I see the timeout happening 10 seconds after it probably got the first
message on the connection/channel.
Although according to the logs it processed 51 tasks. That seems odd... I'm
going to
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #28 from David Cook ---
Looks like the test plan is missing a step since without restarting the koha
background job worker you'll just get the following:
Exception 'Koha::Exception' thrown 'test is not a valid job_type'
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #27 from David Cook ---
(In reply to Jonathan Druart from comment #25)
> I am giving up, need help.
>
> I wrote this script to help adjusting the worker code and see how things
> went.
>
> To test:
> Edit
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #26 from David Cook ---
(In reply to Jonathan Druart from comment #17)
> And what about the 30 minutes timeout?
That's always a danger. If 1 message takes 30+ minutes to process, then we'll
have problems when using a
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32558
--- Comment #21 from David Cook ---
(In reply to Jonathan Druart from comment #14)
> From
> https://www.grzegorowski.com/rabbitmq-406-channel-closed-precondition-failed
>
> "You have to ACK messages in same order as they arrive to
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32573
--- Comment #4 from David Cook ---
If you were doing a big batch record modification and you suffered a power
outage on the machine where the background job worker is running, then that
task can't be re-started since the RabbitMQ
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32573
David Cook changed:
What|Removed |Added
CC||dc...@prosentient.com.au
---
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32393
--- Comment #15 from David Cook ---
We need to keep the fork, and catching all exceptions makes sense to me. You
could say that the background job worker is really a background job server and
servers really shouldn't go down. They
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4330
--- Comment #50 from David Cook ---
(In reply to Katrin Fischer from comment #49)
> Is this still something we shoudl/could fix?
I wonder this as well. I wonder if Catalyst's lawyers could advise on this one.
Copyright statements in
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24679
David Cook changed:
What|Removed |Added
CC||dc...@prosentient.com.au
---
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532
--- Comment #929 from Aleisha Amohia ---
(In reply to Jonathan Druart from comment #928)
> koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-course-details.tt
>
> -[% INCLUDE 'item-status.inc'
>
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10567
Katrin Fischer changed:
What|Removed |Added
Status|NEW |RESOLVED
19 matches
Mail list logo
