For sure it's a firewall problem... the FW will close the connection
but Apache won't know about it. You can also see this
happen when using mod_jk and AJP.
Other than getting a non-brain-dead FW, totally disabling the
connection pool is the work around.
On Jan 29, 2013, at 11:25 AM,
Hi Jim,
You say there is a workaround with disabling the connection pool == How can I
do that ?
Thanks
-Message d'origine-
De : Jim Jagielski [mailto:j...@jagunet.com]
Envoyé : mercredi 30 janvier 2013 13:36
À : dev@httpd.apache.org
Objet : Re: Apache 2.2 mod_proxy fails to send Fin
On Wed, Jan 30, 2013 at 8:03 AM, sebastien.allam...@orange.com wrote:
Hi Jim,
You say there is a workaround with disabling the connection pool == How can
I do that ?
See disablereuse option in ProxyPass/ProxySet (scoll down to table
here
On Tue, Jan 29, 2013 at 6:25 AM, sebastien.allam...@orange.com wrote:
Hello,
** **
I’ve got an issue with mod_proxy, on eavy load, I have a lot of HTTP 503
response.
** **
When looking in detail on requests, we can see that mod_proxy don’t close
properly the request (it waits
