0
Reply

TCP CLOSE_WAIT for ever

Jason

Jason

Jul 28 2009 10:54 AM
5.2k
We have a third party WMS that for some reason doesn't handle it's tcp connections correctly.  It has a server that servers requests from handheld units, but doesn't always close the connection after a handheld disconnects.  Connections get stuck in CLOSE_WAIT status forever and eventually all the availible connections get used up and the handheld units can't reconnect.   

My question is this: is there a way to force connections in CLOSE_WAIT that are in a different app domain to close?