Re: WSAENOBUFS on winsock client application
- From: h.melchin@xxxxxxxxxxxxxxxxxxxxxxxxx
- Date: Fri, 9 May 2008 00:59:16 -0700 (PDT)
The other parts of the application (client winsock threads) continue
working without problems.
The thread that causes the error is furthermore not able to connect to
the server any more (while other established connections are working
fine)
The connection-attempt is being retried every minute but for that
thread the behaviour is always the same after the first occurance of
this error. It just repeats forever.
What kind of (winsock-) leak may be left after shutting down the
socket as documented by MS, waiting for any I/O operation to terminate
and calling closesocket ?
I've done a lot of stress testing, but the problem only occurs at the
customer side, I cannot reproduce it here.
It seems to me that the network is not very steady there..., even
though the application should not hang.
thanks !
H.
.
- References:
- WSAENOBUFS on winsock client application
- From: h . melchin
- Re: WSAENOBUFS on winsock client application
- From: Volodymyr M. Shcherbyna
- WSAENOBUFS on winsock client application
- Prev by Date: RE: RPC method is throwing exception (1732) RPC_S_UNSUPPORTED_TYPE
- Next by Date: WSAENOBUFS on winsock client application
- Previous by thread: Re: WSAENOBUFS on winsock client application
- Next by thread: WSAENOBUFS on winsock client application
- Index(es):
Relevant Pages
|