Hi, I haven't read the full posting, but I recognise the error #.
10053 are common in the last week with a big client of ours.. What causes them (in our case) is poor connectivity including firewalls. The computer trying to connect can't make a connection, but it isn't reaching the destination. I can explain in detail the packet sequence that causes this but it would be boring. This error is practically the same as connection refused, but that a firewall in the middle is probably doing the refusal. Regards David Wilfried Mestdagh wrote: > Hello, > > >> 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 >> > > The 10053 is in OnSessionClosed yes ? So all you have to do is reconnect > over there. > > >> there are CLOSE_WAIT state sockets aggregating and when they reach a certain >> amount, Accept() no longer works! >> > > You mean at server side ? Correct if there are too many sockets in use > (including the sockets in WAIT state) they use non pagable memory. When > all memory is used you cannot create a socket until memory becaumes > available again. So the server has to have the amount of memory needed > for his maximum predicted amount of clients and yes with some reserve > because connection can break. > > --- > Rgds, Wilfried [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > http://www.mestdagh.biz > > -- 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