View Issue Details

IDProjectCategoryView StatusLast Update
0001148Double CommanderPluginspublic2020-06-19 21:52
Reporterhtd Assigned ToAlexx2000  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
ProjectionnoneETAnone 
PlatformWindowsOSWindows 10OS Version10
Product Version0.6.4Product Build2015/07/12 
Summary0001148: Application stops responding after FTP session times out
DescriptionMost of the FTP servers times out the sessions when they don't receive keep-alive packets, and DC FTP plugin doesn't have the option to provide such packets.

The correct behavior in such case would be either reporting an error to the user (session expired) or offering the user the option to log on again.

The observed behavior is the application stops responding for several minutes.
Steps To Reproduce1. Connect to any FTP server using built-in FTP plugin
2. Wait for 15 minutes (should be enough)
3. Try to copy a remote file or open a remote directory
Additional InformationThis issue may also occur on common network errors. Application should either report errors, or try to retry operation - but not indefinitely. It should be also reasonable hardcoded or configurable timeouts for IO operations. When there is no response from the server in 10 seconds it means the server is down. Even if it responded after 30 seconds - it's overloaded and most probably temporarily incapable to complete desired operations.
TagsNo tags attached.
Fixed in Revision
Operating systemWindows
WidgetsetWin32
Architecture64-bit

Activities

Alexx2000

2015-08-16 16:05

administrator   ~0001531

Try with version 0.6.5. I found that ftp had very long timeout (5 minutes). I changed it to 30 seconds.

Alexx2000

2016-05-09 21:03

administrator   ~0001710

No feedback

Issue History

Date Modified Username Field Change
2015-08-10 12:31 htd New Issue
2015-08-16 16:05 Alexx2000 Note Added: 0001531
2015-08-16 16:05 Alexx2000 Status new => feedback
2016-05-09 21:03 Alexx2000 Note Added: 0001710
2016-05-09 21:03 Alexx2000 Status feedback => resolved
2016-05-09 21:03 Alexx2000 Resolution open => fixed
2016-05-09 21:03 Alexx2000 Assigned To => Alexx2000
2020-06-19 21:52 Alexx2000 Status resolved => closed