🚀 go-pugleaf

Hans,

Thank you for replying, I appreciate it very much. This problem is really 
causing my hair to turn grey and I really need to figure it out.


> 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 ?

Well I can't really determine how many connections there are when the 
problem happens but I at any given point I could have 40 to 80+ machines 
connected.

Once connected the clients stay connected for hours at a time.

> 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?

Yes, once the problem starts a client may connect but in a very short time 
the error occurs.
Also once the error starts all the previos clients start suffering the 
problem, then they become dissconnected and now a really bad cycle starts as 
they all begin to reconnect and the error occurs which means they disconnect 
again and the cycle starts.

It effects all the clients, not a specific client.


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

No, once the problem starts all clients are effected, new clients, old 
clients, all clients.

Its like the Host Socket has gone ito some kind of error and it effects all 
clients, both connecting and those previously connected.

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

Well what happens is the client detects the socket disconnect, and, once 
this happens the client attempts to reestablish connection to the host. The 
gets a connection, and a couple of messages are transmitted back and forth 
and then the error happens, the client disconnects, the cycle starts over 
again.



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

Ummmm, no, as this will be a very difficult thing to do as the problem is 
happening at a client site.

I do have the same software running at other sites without any of the above 
problems. But what I don't understand is why it could possibly be happening, 
and also, once it starts to happen what can I do with the host application 
to attempt to correct the situation.

Again, thanks Hans for trying to help me with this nasty problem.

Mike





"Hans Galema" <notused@notused.nl> wrote in message 
news:42c653f0@newsgroups.borland.com...
> 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.