Re: Process not always exiting
The lingering sockets don't cause the app exit to hang.
It's a deadlock in one of DllMain/DLL_PROCESS_DETACH. I would guess, someone
is trying to wait on a thread handle.
"Kellie Fitton" <KELLIEFITTON@xxxxxxxxx> wrote in message
news:1134534294.721335.267820@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> Well... when a TCP socket is closed, the socket enters into the
> FIN-WAIT-1 that makes sure all the sent data have been delivered,
> and then enters into the FIN-WAIT-2 until every thing has been
> received, then the TCP sends the final ACK and goes into TIME-WAIT
> state, to make sure the other side has received this final ACK.
>
> However, during the TIME-WAIT if the TCP does not receive another
> FIN segment, it assumes the other side has received the final ACK,
> and it will close gracefully, this of course applies only to the
> TCP that was first to close the connection, and the TCP which is
> notified of the connection shutDown does not enter the TIME-WAIT,
> which specified by the TCP standard, this should be 4 minutes.
>
> Perhaps if you use a netWork sniffer or monitor you might be able
> to determine the real cause of the problem.
>
> Hope these information helps,
>
> Kellie.
>
.
Relevant Pages
- Re: [6.x] problem with AIO, non-blocking sockets on freebSD and IE7 on windows.
... Yes, Blame Microsoft, but we are breaking the TCP spec, not them. ... A TCP socket isn't the same thing as a named pape or FIFO. ... Using non-blocking I/O does not mean one can suddenly shortcut the FINWAIT-1 and FINWAIT-2 states before going into TIME_WAIT, nor the 2 * MSL timeout before the TCP control block is allowed to go away. ... Otherwise, you might end up sending a RST to a dup'ed packet like a stray ACK, which seems to be almost exactly the problem at hand. ...
(freebsd-net) - Re: [6.x] problem with AIO, non-blocking sockets on freebSD and IE7 on windows.
... Yes, Blame Microsoft, but we are breaking the TCP spec, not them. ... A TCP socket isn't the same thing as a named pape or FIFO. ... Using non-blocking I/O does not mean one can suddenly shortcut the FINWAIT-1 and FINWAIT-2 states before going into TIME_WAIT, nor the 2 * MSL timeout before the TCP control block is allowed to go away. ... Otherwise, you might end up sending a RST to a dup'ed packet like a stray ACK, which seems to be almost exactly the problem at hand. ...
(freebsd-net) - Re: TCPIP Default keep alive question
... since last December we have been getting ASOD abends in certain CICS ... Did you mean to alert us to the possibility that the *partner* TCP ... SO_KEEPALIVE socket option and do not override the interval using the ... TCP keepalive probes end TCP connections after a period of inactivity. ...
(bit.listserv.ibm-main) - Re: TCPIP Default keep alive question
... Did you mean to alert us to the possibility that the *partner* TCP application ... SO_KEEPALIVE socket option and do not override the interval using the ... TCP keepalive probes end TCP connections after a period of inactivity. ... If the TCP_KEEPALIVE socket option is not used to specify the probe ...
(bit.listserv.ibm-main) - Re: Socket stuck with puts over ADSL line
... gets stuck with the puts command within the filevent writeable ... Is the socket configured as -blocking 1? ... local buffer would fill rapidly, ... buffered portion across the WAN as its own TCP packet, ...
(comp.lang.tcl) |
|
