FIN_WAIT_2 and a socket connect that takes an age to close.
From: Andy Coates (nothanks_at_nowhere.com)
Date: 06/11/04
- Next message: cyberninja: "Re: A question on mailslot"
- Previous message: novice_win_snmp: "Re: Snmp Service and Community String"
- Next in thread: Arkady Frenkel: "Re: FIN_WAIT_2 and a socket connect that takes an age to close."
- Reply: Arkady Frenkel: "Re: FIN_WAIT_2 and a socket connect that takes an age to close."
- Reply: Alan J. McFarlane: "Re: FIN_WAIT_2 and a socket connect that takes an age to close."
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 11 Jun 2004 15:11:07 +0100
Hi,
I'm using Overlapped IO and completion ports to handle socket connections
coming into a server application. On shutdown I iterate over any current
socket connections calling ::shutdown() on each socket. I then wait until
all pending overlapped operations complete.
This normally works fine, but I have one client application (for which I
can't easily get source) that causes problems on shutdown. This particular
socket takes ~2minutes before the queued read operations complete. When I
run netstat I see that the socket is in the FIN_WAIT_2 state, which I
understand to mean that it has received the ACK from the client.
Why is this socket taking so long to shutdown?
Thanks for any help or advice you can give,
Andy
- Next message: cyberninja: "Re: A question on mailslot"
- Previous message: novice_win_snmp: "Re: Snmp Service and Community String"
- Next in thread: Arkady Frenkel: "Re: FIN_WAIT_2 and a socket connect that takes an age to close."
- Reply: Arkady Frenkel: "Re: FIN_WAIT_2 and a socket connect that takes an age to close."
- Reply: Alan J. McFarlane: "Re: FIN_WAIT_2 and a socket connect that takes an age to close."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|