Re: What situations cause WSAECONNABORTED to be returned by recv?

>From MSDN :

Software caused connection abort.
An established connection was aborted by the software in your host
computer, possibly due to a data transmission time-out or protocol error.

Local TCP stack send up that error if it decided ( due to 2 reasons ) that
no peer exist on the opposite side
Arkady

"RichK" <nospam@xxxxxxxxxx> wrote in message
news:ep$lCxv2FHA.3704@xxxxxxxxxxxxxxxxxxxxxxx
> I'm trying to identify why I'm seeing a WSAECONNABORTED failure in recv().
>
> Some causes that I seem to have identified are:
> 1) sufficient packets being dropped by the network that retransmission
> logic fails.
> 2) calling shutdown(SD_SEND) on the socket, and the peer application never
> responds to this shutdown with a call closesocket() or shutdown(SD_SEND)
> (This would cause a FIN to be sent, that was never responded to with a
> FIN )
>
> Other than routers dropping packets, and a peer application not closing
> sockets, does anyone know of other situations that would cause recv() to
> fail with WSAECONNABORTED?
>
>
>
>


.

Relevant Pages

  • Re: close and O_NONBLOCK on TCP/IP socket in Linux
    ... >> reading what i am interested in from the peer. ... If they don't read, but only write, then they won't see FIN, and ... >> to report the FD as writable after nonblocking shutdown of write?. ... OP the socket is closed after he got what he wanted. ...
    (comp.unix.programmer)
  • Re: How to terminate a socket in CLOSE_WAIT state
    ... CLOSE_WAIT is the state in which a socket may remain indefinitely -- more ... FIN from its peer. ... with zero or non-zero timeout. ...
    (microsoft.public.win32.programmer.kernel)
Loading