🚀 go-pugleaf

mike wrote:

> I have a central host that allows many clients to connect in a blocking 
> socket manner, so I am creating a thread for each active client connection. 
> So what happens is all works well for a number of hours then the 10053 
> errors start.

How many connections are there usually whan that happens ? How do
the clients behave: do they come and go within a few minutes or
are they staying for hours ?

> This of course breaks the socket connection to the client and 
> then the client attempts to connect again. When the client connects the 
> 10053 errors persist and clients cannot connect.

So such a client can reconnect but then after a short time there is
the same error ? Is this for some specific clients or for all then?

What about clients that did not connect before the errors stated. Are
they handled ok ?

> So can someone assist me in understanding why this error would start 
> occurring, and then once they start how do I get my application back into 
> the state where connections can resume.

Aha. So a client can not resume ? Please explain in detail.

Did you do test with all clients and the server on the same machine ?

Hans.