🚀 go-pugleaf

Well it seems I have solved the problem.

I discovered (I dont know how I missed this one, too much in the log files 
maybe) that there was a slight issue with the server app that caused a 
failed connection once in a long while (socket error 10061, Connection 
Refused).
This happened every time that this strange behaviour of my service occurred.
Seems what was happening is that for a moment the server was not accepting 
connections and at that moment my service tried to connect.  I then "timed 
out" after 10 seconds and tried to disconnect because I wasn't getting any 
data.
Attempting to disconnect at this point for some reason caused everything to 
stop dead.

First I simply removed the call to MyDisconnect so that even though I timed 
out, I did nothing about it.
This allowed the TIdTelnet component to "recover" from the exception on its 
own and processing continued as normal.

Next I went and cleaned up the code in the server just a little, which now 
seems to prevent the 'connection refused' error from happening at all 
(server was not releasing the old connection correctly under all 
circumstances and so could not pick up a new one).

It's now been running for 15 hours straight with not a problem in sight.
And thats with connecting and disconnecting twice every 20 seconds.

So far it looks good.

This make any sense?

Andre'