Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#5172 closed Bug report (fixed)

MAC SnowLeopard & FZ 3.3.1 Resume error

Reported by: Petr Ungern Owned by:
Priority: normal Component: FileZilla Client
Keywords: Resume Cc:
Component version: Operating system type: OS X
Operating system version: SnowLeopard 10.6.2


If Internet connection breaks, any queue breaks too! There is no way to resume that transfer besides closing FZ, restarting, and new uploading then resume works BUT not always sending the file then completely! File broken!
Stopping Queue and then starting again gets always an error:
ftpcontrolsocket.cpp(1819): Waiting for replies to skip before sending next command... caller=0x10ae028

I would real recommend to add to the Process Queue etc; something like Pause Queue, and Resume Queue, and to secure that if any Internet connection was broken whilst transferring, that after some timeout and Internet connection is resumed transfer is restarting automatically and not as now crash the connection with that ftpcontrolsocket error! Our Internet connection cuts often off and comes back after 1-2 minutes only...

Change History (4)

comment:1 by Tim Kosse, 14 years ago

Status: newmoreinfo

Do you have timeouts disabled in FileZilla?

If timeouts are enabled, FileZilla will notice that the connection has stalled. However if you have timeouts disabled and the connection gets silently dropped, FileZilla will dutifully wait until all eternity for data that will never arrive.

comment:2 by Petr Ungern, 14 years ago

Resolution: fixed
Status: moreinfoclosed

Ok that timeout tip solved it. Many tanks. Anyway I would like to recommend to add an transfer suspension and resume possibility for the queue files (Pause queue, resume queue). That would be very helpful, not only for me I guess. Thanks for your kind and fast attention.

comment:3 by Tim Kosse, 14 years ago

The "process queue" button in the toolbar already does that.

comment:4 by Petr Ungern, 14 years ago

Ok thanks again, sometimes I am a bit .... Nu tested it and it works well. Many thanks again.

Note: See TracTickets for help on using tickets.