🚀 go-pugleaf

Hi,
thak you for you answer.

Remy Lebeau (TeamB) ha scritto:
> Raffaele Pantaleoni <pantaraf@yahoo.it> wrote:
> 
>>    Msg=AThread->Connection->ReadLn("",5);
> 
> You did not specify any terminator.  Indy will use LF by default.  If the client sends lots of data without sending LF then you could be filling up memory.
I was aware about this, but when the error comes out nothing is coming
from the client, the link is idle. Moreover if the link is populated by
data, no errors come out.

>>  catch (Exception &exception)
> 
> If an Indy exception occurs (one that is derived from EIdException), you should re-throw the exception so that the server knows that something went wrong with the connection.  If you do not do that, or if you do not disconnect the connection manually, then the thread will never terminate properly.
Thank you for your complete answer. I intentionally cut out the rest of
my catch routine for easiness of reading, the rest of the catch routine
is about closing the connection and cleaning.

I think that I solved my problem, I raised the readln timeout up to 5000
and the server is running with an idle client connected for 15 hours
now. No "Out of memory" errors came out in the meantime. I will try also
a blocking readln, as you suggested.

I noticed that using a 1 ms timeout the "Out of memory" exception comes
out about every 5-8 minutes (using the very same conditions). While
using a 5 ms timeout it comes out in a range starting from 1 up to 3 hours.

Thank you.
Raffaele Pantaleoni