"Andreas Stroebel" <support@ascomp.de> wrote in message
news:47687380$1@newsgroups.borland.com...
> It's a bug in TIdFTP. Occured on my own FTP server and on
> several customer's FTP servers, too.
Well, then you still need to provide a packet trace in order to diagnose the
communication anyway. Unless you debug into the source code yourself and
find where the hang is.
> Doesn't help. I'm using 10000 for read and transfer timeout, but it
> doesn't have any effect. It just hangs.
The only way it can hang indefinately is if the hang is occuring when
writing data to the server, not reading from it, as there is no
WritingTimeout in Indy.
Unless you are deadlocking the code yourself in an event handler.
> OnWorkEnd will be called after the entire file has been
> uploaded but nothing else happens any more.
Do you get any OnDataChannelDestroy or OnStatus events?
For OnWorkEnd to fire, but Put() to not exit, that would indicate that
TIdFTP is waiting for a reply from the server that never arrives, like I
said earlier. But then, the ReadTimeout would take effect in that case,
aboring the wait when the timeout elapsed. So without more information,
this would seem to be a potential blockage at the OS level, not inside of
TIdFTP's code.
Gambit
