|
Hi, We are using version 2.5.3009.0 of Rebex.Ftp.Net.dll. We have found that for large transfers (200+ MB mov files) we occasionally get a "Timeout exceeded" exception. This does not occur all the time. This occurs on the Ftp.Put() command and it can occur at different points in the file transfer. Is there a property that needs to be set to increase the timeout? JD |
|
I'm not 100% certain yet, but this seems to resemble an issue our clients encounter once in a while. Some badly behaved firewalls or routers silently close the main FTP connection while a data transfer is in progress because of inactivity - even though the main FTP connection is actually supposed to be inactive while the transfer is in progress (it uses a separate TCP connection). Rebex FTP includes a workaround for this issue, but it doesn't work reliably with all FTP servers so it's disabled by default. To enable it, use this code: This will cause a dummy NOOP command to be sent every 600 seconds (10 minutes) - you can also specify a longer interval by changing the value of Ftp object's KeepAliveDuringTransferInterval property. Does enabling this option help? |
Once the failure has occurred, using another FTP client (fireZilla for example), the ftp goes through.
I am looking through the logs I created and most of the failures occurs on exactly 50 mins of the ftp.Put(). Although some failures on the same file occurred on 25 mins and 45 mins from the start of the put command.
Further to my last comment, failure on 50 mins is the initial problem. The other timeout periods may be a consequence of our FTP server behaving incorrectly after the first failure.