🚀 go-pugleaf

"Andre' Burke" <no.spam@spam.no> wrote in message
news:44f7d1ac$1@newsgroups.borland.com...

> I can then see it going into the MyDisconnect function and calling
> the disconnect. I write a log message right before and directly after
> the actual diconnect call and the log file shows the one before it
> and nothing after that.

In order for that to happen, the TIdTelnet's internal reading thread would
have to be deadlocked.  Under normal situations, disconnecting the socket
would terminate the thread immediately, but if the thread is blocked then it
would not be able to detect the socket being closed, which would in turn
block Disconnect() because it waits for the thread to terminate before then
exiting.

> In fact I have added another timer to the form that simply fires once
> a second and writes the state of the original timer to the log file, eg
> whether it is enabled or not.
> Even this extra timer stops at this point.

Sounds like you are deadlocking the main thread as well, since TTimer is a
message-based timer.  If you are calling Disconnect() in the context of the
main thread, as the internal reading thread is blocked so that it cannot
terminate itself, then Disconnect() is going to be blocked, and thus prevent
the main thread from processing pending messages.

> I originally had a similar problem when I tried to disconnect from
> inside the OnDataAvailable event.

You cannot do that.  That is a guaranteed deadlock, since Disconnect() would
be waiting on the thread to terminate, but the thread would be waiting for
Disconnect() to exit.

> This seems to be something similar, except that the disconnect
> is now no longer being called in the OnDataAvailable method
> but rather in the timer.

That does not negate the possibility of the reading thread still becoming
deadlocked.

> It seems as if the Telnet component recieves the incoming data, but
> for some reason gets stuck and doesnt call the OnDataAvailable
> method.

That cannot happen.  What is more likely the case is that the
OnDataAvailable event handler is becoming deadlocked.


Gambit