[Koha-bugs] [Bug 12005] Zebra searches sometimes fail silently under Plack

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

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12005

--- Comment #1 from Jacek Ablewicz <abl at biblos.pk.edu.pl> ---
(In reply to Magnus Enger from comment #0)

> A quick and dirty fix can be found here:

Works for me (3.14.5, apache + mod_perl). Or at least it seems to - hard to
tell for sure, as this nasty bug does recur in semi-random fashion. Sometimes
the 1st failed search occurs after a couple of minutes after server restart,
and sometimes it works seemingly fine for hours.. I got an impression that as
long as all processes/workers are relativelly busy, this issue is much harder
to reproduce. Also it seems to happen somehow more often / earlier in plack +
starman test configuration (or maybe it is just a coincidence).

This Q&D fix is kind of ugly, though ;). It does quickly result in a lot of
accumulated zebra processes (never to be used again, with postponed death
sentences). Wouldn't it be better to destroy the Zconn connection as soon as
possible when it is no longer needed? Sadly, ZOOM::Connection object does not
automatically disconnect on DESTROY() like DBI does; I guess some kind of
wrapper class may be needed to solve this.
Also I wonder what kind of performance impact this (= not caching zebra
connections at all) may have in plain CGI installations. Perhaps some
plack-related fixes in the code should be controlled by new configuration
setting (preferably in koha-conf.xml) which will indicate that system is, or is
not running in persistent environment (and what kind: plack/*,
mod_perl/persistent, mod_perl/semi-persistent ..).

Btw, bug 11701 (pushed yesterday) got me thinking: looks like Zconn caching was
not plack compatible at all. May it be somehow related to this bug (especially
sync vs async thing)?

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