> 3) So why are these connections hanging around?
>
> Well this part of my knowledge is a bit shaky. Basically clients enter
> the TIME_WAIT state after and active connection closes. I guess it is
> time to stand on the shoulders of others ... MS knowledge base article
> Q137984 has the following paragraph about this condition:
>
> NOTE: It is normal to have a socket in the TIME_WAIT state for a long
> period of time. The time is specified in RFC793 as twice the Maximum
> Segment Lifetime (MSL). MSL is specified to be 2 minutes. So, a socket
> could be in a TIME_WAIT state for as long as 4 minutes. Some systems
> implement different values (less than 2 minutes) for the MSL.
The proper (soft) closing of a socket generally involves initiating a
shutdown sequence where the connection lingers around for a while to make
sure everything that was meant to be sent actually gets there. A lot of
people (myself included) have a tendacy to do an immediate hard closure of
the socket though. Less hassle.
That they linger around means the some coder somewhere probably has read a
few tcp books and knows what they're doing. :)
> 4) Why is your web server not serving up some images ?
>
> I have no idea. But having these 200 connections from AOL doesn't sound
> like a cause for alarm if your site gets some good traffic. These
> connections most likely aren't killing your server.
Hrm. Sounds a bit like the server is getting hammered. It's socket queue is
being exhausted. It's timing out in the middle of transfers. etc. That's
just a guess though.
--min
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
