From: Chuck Murcko <chuck@n2k.com>
Message-Id: <199701080441.XAA13362@spudboy.telebase.com>
Subject: Re: server timeouts and FIN_WAIT_2
To: new-httpd@hyperreal.com
Date: Tue, 7 Jan 1997 23:41:37 -0500 (EST)
In-Reply-To: <199701080418.XAA11990@spudboy.telebase.com> from "Chuck Murcko"
 at Jan 7, 97 11:18:48 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

No difference without lingering close. OTOH, my internal proxy's FIN_WAIT_2
state connections are all from WIN95 boxes. 8^)

Chuck Murcko liltingly intones:
> 
> Oh, right. Crap. I can try this. Will do now, in fact.
> 
> Marc Slemko liltingly intones:
> > 
> > lingering close; could be an obscure implementation bug in apache code or,
> > more likely, bugs in various OSes that don't do a half-close properly. 
> > Has anyone with the problem tried compiling with NO_LINGCLOSE to see if
> > it goes away?
> > 
> > On Tue, 7 Jan 1997, Chuck Murcko wrote:
> > 
> > > Is there something specific about the way Apache handles timeouts and/or
> > > connection closes now that could be causing connections left in FIN_WAIT_2?
> > > I can't see anything obvious in the source, but these are areas of the
> > > code I'm not intimately familiar with.
> > > 
> > > Did the basic way timeouts or closes are handled by the server change
> > > between Apache 1.1.1 and Apache 1.2 change in any way?
> > > 
> > > We seem to have some folks in c.w.i.s.u. who are convinced that this is all
> > > a problem with Apache 1.2.
> > > 
> > 
> > 
> 

chuck
Chuck Murcko	N2K Inc.	Wayne PA	chuck@telebase.com
And now, on a lighter note:
Every improvement in communication makes the bore more terrible.
		-- Frank Moore Colby