https://bz.apache.org/bugzilla/show_bug.cgi?id=65832
Bug ID: 65832
Summary: purge keepalive connections before 0 idlers?
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: enhancement
Priority: P2
Component: mpm_event
Assignee: bugs@httpd.apache.org
Reporter: cove...@gmail.com
Target Milestone: ---
When event hits zero idlers, a keepalive connection that becomes active can be
abruptly closed in response to the new request being readable.
/* If we don't get a worker immediately (nonblocking), we
* close the connection; the client can re-connect to a
* different process for keepalive, and for lingering close
* the connection will be shutdown so the choice is to
favor
* incoming/alive connections.
*/
get_worker(&have_idle_worker, blocking,
&workers_were_busy);
if (!have_idle_worker) {
shutdown_connection(cs);
}
I don't know if normal browser requests will retry idempotent requests
transparently, but something like XHR will require error handling to do it.
It seems like if we are "approaching" zero idlers (and know that we have an
AsyncRequestWorkerFactor > 1) it would be better to shed some or all keepalive
connections earlier, before we have to shutdown ones that have just been used.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
