At Sat, 30 Jun 2012 00:33:36 +0200, Rüdiger Asche wrote:
> All of this runs fine for a while, until ALL of the stress clients
> begin to raise WSAEADDRESSINUSE exceptions. [...] in the case of
> tcp-connect(), I assume that the call with no local port translates
> to a bind() with port 0 which inst
Matthew can address the Racket internals questions, but one thing I'd
check, if you haven't already...
At the moment of the error, have all the free TCP ports on one of the
involved nodes been exhausted? You can probably check this on the
individual hosts close enough to the moment of the err
Hi there,
today's bug from hell might not be a Racket related issue (to me it seems more
of a Windows type of thing), but maybe somebody has already come across
something similar, so here goes:
I have a Racket application serving as a stress test against a TCP server, that
is, the Racket appli
3 matches
Mail list logo
