Re: [racket] strange issue with tcp-connect on Windows...

2012-06-30 Thread Matthew Flatt
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

Re: [racket] strange issue with tcp-connect on Windows...

2012-06-29 Thread Neil Van Dyke
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