You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2021/10/19 15:07:26 UTC

[Bug 65642] New: mod_proxy: retry-directive does not work anymore

https://bz.apache.org/bugzilla/show_bug.cgi?id=65642

            Bug ID: 65642
           Summary: mod_proxy: retry-directive does not work anymore
           Product: Apache httpd-2
           Version: 2.4.51
          Hardware: Other
            Status: NEW
          Severity: major
          Priority: P2
         Component: mod_proxy
          Assignee: bugs@httpd.apache.org
          Reporter: max.moebius1@gmail.com
  Target Milestone: ---

Until Version 2.4.16 (last version I checked) the reverse proxy deactivated a
worker in case the URL was down for "retry"-Seconds. 

Configuration:
ProxyPass       /YYYYY/XXX/     http://XXX:1234/ retry=5 connectiontimeout=30


Example from 2.4.16 Log (subsequent requests to the same backend are answered
immediately with return-code 503):
[Tue Sep 21 10:42:35.663877 2021] [proxy_http:error] [pid 9144:tid 8124]
[client x.x.x.x:50803] AH01114: HTTP: failed to make connection to backend: XXX
[Tue Sep 21 10:44:12.192333 2021] [proxy:error] [pid 9144:tid 7668] (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.  : AH00957: HTTP: attempt to connect to y.y.y.y:1234
(XXX) failed
[Tue Sep 21 10:44:12.192333 2021] [proxy:error] [pid 9144:tid 7668] AH00959:
ap_proxy_connect_backend disabling worker for (XXX) for 5s
[Tue Sep 21 10:44:12.192333 2021] [proxy_http:error] [pid 9144:tid 7668]
[client x.x.x.x:50837] AH01114: HTTP: failed to make connection to backend: XXX
[Tue Sep 21 10:44:12.736341 2021] [proxy:error] [pid 9144:tid 5972] AH00940:
HTTP: disabled connection for (XXX)
[Tue Sep 21 10:44:12.752309 2021] [proxy:error] [pid 9144:tid 5972] AH00940:
HTTP: disabled connection for (XXX)
[Tue Sep 21 10:44:12.769313 2021] [proxy:error] [pid 9144:tid 5972] AH00940:
HTTP: disabled connection for (XXX)
[Tue Sep 21 10:44:12.785412 2021] [proxy:error] [pid 9144:tid 5972] AH00940:
HTTP: disabled connection for (XXX)


Current Version 2.4.51 does not respect the retry-setting. It does not disable
the worker. Subsequent requests have to wait for 20s:

[Tue Oct 19 10:17:30.891993 2021] [proxy_http:error] [pid 15356:tid 7156]
[client x.x.x.x:51075] AH01114: HTTP: failed to make connection to backend: XXX
[Tue Oct 19 10:17:51.910382 2021] [proxy:error] [pid 15356:tid 8112] (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.  : AH00957: http: attempt to connect to
y.y.y.y:1234 (XXX) failed
[Tue Oct 19 10:17:51.910382 2021] [proxy_http:error] [pid 15356:tid 8112]
[client x.x.x.x:51079] AH01114: HTTP: failed to make connection to backend: XXX
[Tue Oct 19 10:18:12.975273 2021] [proxy:error] [pid 15356:tid 8112] (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.  : AH00957: http: attempt to connect to
y.y.y.y:1234 (XXX) failed

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org