[Koha-bugs] [Bug 15006] Need to distinguish client timeout from login timeout

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

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

Larry Baerveldt <larry at bywatersolutions.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |larry at bywatersolutions.com

--- Comment #9 from Larry Baerveldt <larry at bywatersolutions.com> ---
Like Kyle, I am concerned about regression. The issue addressed by Bug 13432
was a very serious one for us, and affected virtually every site using SIP. New
child processes were continually being created throughout the day, and older
child processes were never dying. In some cases the number of SIP processes
would literally max out the RAM. We had to introduce daily restarts of SIP in
our crons, and for some sites, even that was not enough. And Bug 13432 DID fix
that problem. 

As to the problem of the timeout logic causing dropped connections post 13432,
we simply fixed that on our servers by increasing the timeout in the Service
and Institution levels to 360. That worked for most SIP vendors. 

That said, I think this patch would be okay if it includes Kyle's suggestion to
have the client_timeout default to the timeout if not defined.

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