#11138 closed Bug report (rejected)
Unneccesary wait
| Reported by: | mambazo | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | failed timeout reconnect | Cc: | |
| Component version: | 3.24.0 | Operating system type: | Windows |
| Operating system version: | 10 |
Description
When client is idle and disconnects, then you select a different remote directory from the directory-tree, it doesn't reconnect first. You have to wait for the timeout before it will reconnect, or manually disconnect and reconnect.
Logs...
Status: Disconnected from server
Status: Retrieving directory listing of "###"...
Command: cd ".."
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Connecting to ###...
Status: Connected to ###
Status: Retrieving directory listing of "###"...
Status: Listing directory ###
Status: Directory listing of "###" successful
Could it reconnect before trying the command first time round?
I have seen a similar ticket from 11 years ago which was resolved but this it still happening for me. (perhaps 11 years ago it was the Linux version that was fixed? I have no idea.)
Change History (4)
comment:1 by , 8 years ago
| Resolution: | → rejected |
|---|---|
| Status: | new → closed |
comment:2 by , 8 years ago
The first line of the log shows that filezilla was informed of the disconnect (or am I reading it wrong?)
The disconnect isn't what the bug report was initially about though. The bug report is that, even though FileZilla knows it is disconnected, when I navigate to another directory in the tree browser window, it doesn't reconnect before issuing the command.
comment:4 by , 8 years ago
Replying to codesquid:
It's from an unrelated connection.
Forgive me but I don't understand. What other connection?
You need to distinguish a true disconnect from a timeout due to a faulty firewall, NAT router or consumer-grade modem dropping alive connections without informing both peers.
According to the log there's nothing wrong with FileZilla, eventually the connection simply times our because your system did not get informed by some firewall, NAT router or consumer-grade modem that the connection is no longer alive.