🚀 go-pugleaf

Hans,

Thanks for answering. Yes the message description of the error is as 
follows:
WSAECONNABORTED (10053) Software caused connection abort.

Berkeley description: A connection abort was caused internal to your host 
machine. The software caused a connection abort because there is no space on 
the socket's queue and the socket cannot receive further connections.

WinSock description: Partly the same as Berkeley. The error can occur when 
the local network system aborts a connection. This would occur if WinSock 
aborts an established connection after data retransmission fails (receiver 
never acknowledges data sent on a datastream socket).

TCP/IP scenario: A connection will timeout if the local system doesn't 
receive an (ACK)nowledgement for data sent. It would also timeout if a 
(FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will 
eventually timeout if a FIN is not returned).

I am using the TSocketServer from builder not Indy or any anything else.



Mike



"Hans Galema" <notused@notused.nl> wrote in message 
news:42c5783a$1@newsgroups.borland.com...
> mike wrote:
>> I have a site that is getting 10053 errors and I am not sure how to 
>> handle this in my application.
>
> You did a search for what 10053 stands for ? Please supply the description
> also.
>
>> I have a central host that allows many clients to connect in a blocking 
>> socket manner,
>
> Are you using raw sockets or an Indy component or something like that ?
>
> Hans.