Bug 62079 - Connection timeout after 60 seconds
Summary: Connection timeout after 60 seconds
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.4-HEAD
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Depends on:
Reported: 2018-02-05 23:09 UTC by Chandramouli
Modified: 2018-02-07 20:26 UTC (History)
0 users

httpd.conf with default TimeOut (7.74 KB, text/plain)
2018-02-07 20:07 UTC, Chandramouli

Note You need to log in before you can comment on or make changes to this bug.
Description Chandramouli 2018-02-05 23:09:32 UTC
Hi, With the default configuration of httpd.conf file, while submitting POST request the connection gets timeout after 60 seconds, even though back end is still processing the data. The POST request has large data, so it iterates at back end for more processing.
When I add "TimeOut 120" in httpd.conf file then the connection will time out after 120 seconds.

And if I add "Timeout 300" in httpd.conf file then the same request resubmits after every 120 seconds and the connection gets timeout after 300 seconds. In this scenario same request get resubmit 3 times. 

I am looking for the first request to be processed successfully, without connection timeout. could you please suggest.
Comment 1 Eric Covener 2018-02-05 23:16:16 UTC
proxy, cgi, something else? configuration? logs?
Comment 2 Chandramouli 2018-02-07 20:07:40 UTC
Created attachment 35721 [details]
httpd.conf with default TimeOut

httpd.conf with default TimeOut. But connection get timeout after 60 seconds
Comment 3 Chandramouli 2018-02-07 20:10:31 UTC
Please find the attachment for httpd.conf file. It has default TimeOut. With this configuration the connection gets timeout after 60 seconds. If I add "TimeOut 120" or "TimeOut 600" the connection get timeout after 120 seconds. But in any of these scenarios my login session doesn't timeout. Please let me know if you need any more details.
Comment 4 Chandramouli 2018-02-07 20:13:39 UTC
Whenever the connection get timeout then I can find below error in log.

[Wed Feb 07 13:59:26.876526 2018] [proxy_http:error] [pid 4732:tid 848] (OS 10060)A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  : [client ::1:54656] AH01102: error reading status line from remote server localhost:3000, referer: http://localhost/bulk-lookup
[Wed Feb 07 13:59:26.877526 2018] [proxy:error] [pid 4732:tid 848] [client ::1:54656] AH00898: Error reading from remote server returned by /api/bulk-lookup, referer: http://localhost/bulk-lookup
Comment 5 Eric Covener 2018-02-07 20:26:20 UTC
Does increasing ProxyTimeout directly change the behavior?