Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: Fri, 18 Feb 2011 14:46:33 -0500 (EST)
Message-Id: <201102181946.p1IJkXbc002237@thor.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: DO NOT REPLY [Bug 50807] mod_proxy fails to send FIN response when a
 FIN is received from a backend
In-Reply-To: <bug-50807-7868@https.issues.apache.org/bugzilla/>
References: <bug-50807-7868@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=50807

--- Comment #3 from Gregory Boyce <gregory.boyce@gmail.com> 2011-02-18 14:46:32 EST ---
Ah, I see.  It appears that Apache does eventually send a FIN packet the next
time that the specific process attempts to establish a new connection.  Until
that point, both ends of the connection are left in a half closed state until
either the next request triggers the FIN and a subsequent SYN, or the servers
timeout the connection.

This ended up biting us when a load balancer had a very long timeout value (30
minutes) and we were apparently not sending enough requests through in order to
flush out the FINs.  Eventually a request would attempt to reuse the same
source port and the load balancer wouldn't respond to the SYN requests since it
was still waiting on a FIN from us on that source port.

We've worked around it for now by dropping the timeout on the load balancer.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- 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