https://bz.apache.org/bugzilla/show_bug.cgi?id=51814
Hendrik Harms <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |50807 --- Comment #8 from Hendrik Harms <[email protected]> --- The count of CLOSE_WAIT sockets also depends on the chosen mpm-module because the socket pool for backend connection belongs to the process. mpm_prefork handles only one connection per process. So all the other backend connections in the pool may time out and run into state CLOSE_WAIT. They will persist until the same backend will be addressed again or the process was killed. So mpm_prefork will cause a high number of CLOSE_WAIT sockets if you have many different ProxyPass in you config and high settings of MaxSpareServers and MaxRequestWorkers/ServerLimit. e.g.: I've placed a comparison in Bug 50807 between old apache-1.3 and apache-2.4 (mpm_prefork) mpm_worker should have less CLOSE_WAITs cause the chance that a pooled connection will be reused before timed out is much higher. Each thread of one worker process should have access to the whole backend connection pool of its worker process. Referenced Bugs: https://bz.apache.org/bugzilla/show_bug.cgi?id=50807 [Bug 50807] mod_proxy fails to send FIN response when a FIN is received from a backend -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
