>> Why would a servef all into a state in which when a client connects it
>> 10053? I see 10053 when I connect to my customer's site with HTTP client
>> demo after 2 hours! Not 10060, 10061 but 10053!
> A 10053 is 'software caused connection abort'. Normally this is a
> routing or some other malfunction somewhere in between the 2 peer.
> Winsock will generate this error in one of the case you describe in your
> first mail.
So how to overcome it? Francois says the Winsock would timeout at some time
and raise an error but that does not seem to be the case! Seems to me that
there are CLOSE_WAIT state sockets aggregating and when they reach a certain
amount, Accept() no longer works!
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be