Opened 12 years ago

Last modified 12 years ago

#3142 closed Bug report

Timeout to close connection ignored

Reported by: hoch2002 Owned by:
Priority: normal Component: Other
Keywords: Cc: hoch2002, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

filezilla 3.0.0-b7 WinXPhome
The Setting of Transfer-Timeout in seconds greater than 0 up to 9999 is ignored (f.e. 3600) and out of function.
The connection is always closed after some less seconds (about 5 ?), probably by the server. In last versions filezilla was sending LIST, PASV, PWD commands from time to time.
Only 0 seconds seems to work.

Attachments (1)

FileZilla_Timeout-Problem.txt (82.6 KB) - added by hoch2002 12 years ago.
DebugLog_Timeout 0 sec. and 360 sec.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 12 years ago by Tim Kosse

Please attach some logs showing the problematic behaviour.

The logs should be made using debug level 3 which can be enabled
on the debug page in the settings dialog of FileZilla.

The logs have to be complete and unmodified. Do not attempt to
remove or obfuscate any information you might find irrelevant.

If you are worried about posting IP addresses or other
confidential information, mark the tracker item as private.

comment:2 Changed 12 years ago by sf-robot

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Changed 12 years ago by hoch2002

DebugLog_Timeout 0 sec. and 360 sec.

comment:3 Changed 12 years ago by hoch2002

Here the messages with Debug-Level 3 in a File for
Timeout = 0sec. and 360sec.
in both cases after the last filetransfer
any error occurs.

Antwort: 226 File send OK.
Spur: CFtpControlSocket::TransferParseResponse()
Spur: CFtpControlSocket::ResetOperation(0)
Spur: CTransferSocket::TransferEnd(0)
Spur: CControlSocket::ResetOperation(0)
Spur: CFtpControlSocket::SendNextCommand(0)
Spur: FileTransferSend()
Spur: CFtpControlSocket::ResetOperation(0)
Spur: CControlSocket::ResetOperation(0)
Status: Dateitransfer erfolgreich
Spur: CFtpControlSocket::OnReceive()
Antwort: 421 Timeout.
Spur: Unexpected reply, no reply was pending.
Spur: CControlSocket::OnClose()
Fehler: Verbindung mit Server getrennt
Spur: CFtpControlSocket::ResetOperation(66)
Spur: CControlSocket::ResetOperation(66)
Spur: CFtpControlSocket::OnReceive()
Antwort: 421 Timeout.
Spur: Unexpected reply, no reply was pending.
Spur: CControlSocket::OnClose()
Fehler: Verbindung mit Server getrennt
Spur: CFtpControlSocket::ResetOperation(66)
Spur: CControlSocket::ResetOperation(66)
Spur: CFtpControlSocket::OnReceive()
Antwort: 421 Timeout.
Spur: Unexpected reply, no reply was pending.
Spur: CControlSocket::OnClose()
Fehler: Verbindung mit Server getrennt
Spur: CFtpControlSocket::ResetOperation(66)
Spur: CControlSocket::ResetOperation(66)
File Added: FileZilla_Timeout-Problem.txt

comment:4 Changed 12 years ago by Tim Kosse

The server causes the timeout, not the client.

Note: See TracTickets for help on using tickets.