After upgrading to httpd httpd-2.2.3-22.el5 we noticed ProxyTimeout was not being honored and was always sending a 502 after 10 seconds. We've downgraded to version httpd-2.2.3-11.el5_2.4 and it all seems to be working again. I counted like 8 patches to mod_proxy type stuff between those versions though I'm not sure which one is the primary offender.
Thanks for the report. Can you post the complete configuration you're using? There were lots of changes in the timeout config handling though they should all have been improvements.
Created attachment 332393 [details] Current running httpd config file This config works in 2.2.3-11 but not 2.2.3-22
Sorry for the not looking at this sooner. I can't reproduce the problem - can you give the complete proxy config data?
To expand: the timeout used for I/O in the proxy should be, in order of preference: 1) timeout= parameter specified for a specific balancer 2) ProxyTimeout config option (per-server) 3) global Timeout config option so (1) will override (2) if you have any set.
I'm trying to reproduce this in a simplified environment as well. We're in a change freeze window so it could be a week or so out before I can really hit this.
Event posted on 28-09-2009 05:29:05pm BRT by pveiga Even a downgrade did not work. The is some workarround for this issue? This event sent from IssueTracker by pveiga issue 347759 it_file 259911
Event posted on 05-10-2009 12:03:08pm BRT by pveiga Hello! Could you please confirm if the fix will come in RHEL 5.5 or if a workaround could be released before this date. Really thank you. This event sent from IssueTracker by pveiga issue 347759
(In reply to comment #4) > To expand: the timeout used for I/O in the proxy should be, in order of > preference: > > 1) timeout= parameter specified for a specific balancer > 2) ProxyTimeout config option (per-server) > 3) global Timeout config option > > so (1) will override (2) if you have any set. Timeout is not set in this configuration, so ProxyTimeout should be overriding the default. Joe, Have you seen this bug which mentions having issues reading data from POST? https://issues.apache.org/bugzilla/show_bug.cgi?id=41560 Thanks, Adam
Im also curious if this is a client issue where the response times are longer than what Apache expects and then drops the connection. Having the customer provide some tcpdumps to see what we can gather from it. Thanks, Adam
Created attachment 368589 [details] pcap
Created attachment 368603 [details] error log
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.