Bug 52253 - Timeout doesn't work. mod_proxy_balancer strongly depends on TcpMaxConnectRetransmissions in Windows.
Summary: Timeout doesn't work. mod_proxy_balancer strongly depends on TcpMaxConnectRet...
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.21
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-11-28 08:23 UTC by Daniel Charczyński
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Charczyński 2011-11-28 08:23:02 UTC

this problem exists in windows xp. In Linux there is no such problem.

mod_proxy_balancer strongly depends on TcpMaxConnectRetransmissions in Windows during balancing resuest to unavailable backend server.

Because of that fact timeout attribute doesn't work.

steps to redistibute problem.

1. Configure mod_proxy_balancer.
2. Make all back end servers unavailable.
3. Start httpd.
4. Send request to httpd server.

One request to httpd means (TcpMaxConnectRetransmissions +1) requests to unavailable backend server

So one request can take even 1 - 2 minutes depends on windows xp registry configuration.

Do httpd must depend on Windows registry configuration?
Comment 1 William A. Rowe Jr. 2011-11-28 17:26:57 UTC
Apparently not, I would expect that either WSAIoctl or setsockopt would be
the mechanism to alter that behavior.  Neither has such a feature that I
could find.  Feel free to come back with more details.
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:01 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.