| View previous topic :: View next topic |
| Author |
Message |
apollonius
Joined: 24 Jul 2007 Posts: 27 Location: Switzerland
|
Posted: Tue Apr 22, 2008 12:04 am Post subject: Issue with "421 Timeout" - reduce the wait time? |
|
|
Hi
We're downloading files from multiple FTP servers every day. One of the servers quite often causes a timeout with Error 421:
| Code: |
**ERROR Information - 421 Timeout (900 seconds): closing control connection.
|
I would like to reduce this 900-second timeout to a smaller value. The property "Data Timeout(s)" of the Profile is set much lower (65) but that doesn't seem to work with this specific timeout issue.
Can I somehow reduce this timeout time?
We're currently using Automize 7.43. Issue reproducible with "manual" download" via FTP browser; occurs periodically.
The FTP download task is started via a script task and as long as the download task "hangs", i.e. waits for the timeout, the script task is waiting as well.
Thanks and regards,
Silvan |
|
| Back to top |
|
 |
Robert Site Admin
Joined: 25 May 2006 Posts: 1140
|
Posted: Tue Apr 22, 2008 4:23 pm Post subject: |
|
|
I guess that is a command timeout from the server end.. i.e. if no command is sent by the client then the server disconnects the client after 900 seconds of inactivity.
The data timeout of 65 seconds sets the timeout in milliseconds to use when reading from the data connection. This timeout will be set immediately after opening the data connection.
There is no other timeout that can be set looking at the documentation of our 3rd party Ftp api.
Your other options are:
1) run Ftp task in chain and wait for x minutes .. if task does not return , return control to script from chain.
2) run Ftp task as external process (engine menu) . wait time = x minutes. |
|
| Back to top |
|
 |
|