[Mono-dev] TCP Async

[Greg Young]

We are experiencing an issue with async behaviours in sockets (with
SendAsync/callback not Begin/End).

Our visible issue is that when in a send loop we will fail on our
heartbeats. After debugging and counting calls into/out of
SendAsync/callback we see that we are inside of a call to SendAsync
(eg: it never returns, in our case for 10 seconds before we declare
the socket dead). We can duplicate this fairly regularly on
mac/bsd/linux though its nonconsistent (sometimes it may happen
repeatedly other times it works fine). The code does not have such
issues on MS CLR. We are also running on loopback so its unlikely that
an underlying network problem is causing the hang up. The code itself
is fairly straight forward (not that different than the MS example of
the API except that its fully async (separate send/receive loops while
the example is request/response))

I am pulling sources now to build latest but does anyone happen to
know of known issues with this sort of thing?

Cheers,

Greg

-- 
Le doute n'est pas une condition agréable, mais la certitude est absurde.