Re: recv blocks although socket is ready
- From: "314.michael@xxxxxxxxx" <314.michael@xxxxxxxxx>
- Date: 11 Nov 2006 08:14:40 -0800
Because this is a cross plattform application for AIX, Darwin, FreeBSD,
IRIX, IRIX64, Linux, OSF1, SunOS and Windows. I doesnt' make sense to
change something which works on all other plattforms and which ought to
work on Windows too. I'd rather like to know if this is a known issue
with blocking sockets, select and receive. If so I'd implement a
temporary fix until the issue is being addressed. If not, well I guess
I'm on my own ;-)
Michael
Alexander Nickolov wrote:
Why don't you make your socket non-blocking? Then
you'd get WSAEWOULDBLOCK which you can ignore.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
<314.michael@xxxxxxxxx> wrote in message
news:1163184119.063002.123900@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a strange problem using select() and recv(). Intermittedly it
occurs, that even though select() reports the socket to be readable the
following call to recv() blocks. When I shutdown the other peer of the
connection recv() returns and WSAGetLastError() returns WSAESHUTDOWN.
This only occures on our Dell Workstation PWS670. I couldn't reproduce
it on a different machine. I replaced the NIC with a different modell
from a different vendor and installed a different driver but the
problem persited. Running the same app on the same hardware under Linux
I was not able to reproduce the problem though.
Another point which seems worth noting is, that the problem occurs more
frequently when there is some UDP traffic on another socket. This
traffic is consumed by another thread in my app which isn't affected by
the blocking of the main thread.
My setup:
- Dell Workstation PWS670 4xXeon 3.6GHz, 3GB RAM,
- Intel(R) PRO/1000 MTW NIC or ProG-2000S (with Realtek driver)
- Windows XP SP2 (almost) fully patched
Any ideas?
Thanks,
Michael
.
- Follow-Ups:
- Re: recv blocks although socket is ready
- From: Arkady Frenkel
- Re: recv blocks although socket is ready
- References:
- recv blocks although socket is ready
- From: 314.michael@xxxxxxxxx
- Re: recv blocks although socket is ready
- From: Alexander Nickolov
- recv blocks although socket is ready
- Prev by Date: Re: recv blocks although socket is ready
- Next by Date: recv how to
- Previous by thread: Re: recv blocks although socket is ready
- Next by thread: Re: recv blocks although socket is ready
- Index(es):
Relevant Pages
|