🚀 go-pugleaf

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

> What I can't figure out is why the OnDataAvailable would
> deadlock, or for that matter the thread that is calling it.

I see that you have the TIdTelnet::ThreadedEvent property set to true.  That
makes the OnDataAvailable event handler code run in the context of the
reading thread, so you have to make sure that its code is thread-safe.  Is
your logger thread-safe?  What kind of container are you using for your
Incoming_Queue, and is it thread-safe?  I do notice that you are accessing a
couple of counter-related variables in the event handler without protection.

> When this happens, I dont even get this message in the log-file, so
> its not even getting into the code of the OnDataEvent.

Since you have the ThreadedEvent property set to true, then that is only
possible if the reading thread is not receiving any data, meaning that it is
blocked in an idle reading operation.  If actual data is received, then
there is no way the reading thread can become blocked before triggering the
OnDataAvailable event.

With that said, there is another possibility to consider - since you are
using a Telnet component, what does the actual transmitted data look like?
Although it is probably not the case in this situation, it is technically
possible that the data itself could be interpreted entirely as Telnet
control sequences with no application data available.  If that were to
happen, then there would be no reason for the OnDataAvailable to be
triggered.


Gambit