FTPexception, command OK code=200 ???

Question

Hello,

I've got a problem after an file upload (more than 500MB), an exception is throwed just after the upload : FTPexception, command OK code=200 !

It's Ok ... cool, but why it throw an exception? When i try to reupload again, he directly throw me again this exception !

How can I manage this?

Thanks in advance !

St

Answer 1

It shouldn't do that. Are you setting server wakeups or something like that? Looks like a command out of sequence. Can you post a small relevant chunk of the logfile?

Answer 2

Hi,

My name is Charles, I am taking over Bibounce's project, here is a little chunk of the logfile from the exception.
After uploading a heavy file, the next upload call throw the command OK code=200 as an FTPexception.
It looks like server wakeups are sent as you guessed, does the SecureFTPConnection allow me to disable them?

DEBUG [ExFTPPassiveDataSocket] 3 sept. 2007 12:15:07.964 : Created passive data-socket: ProxyConnector=
DEBUG [SSLFTPPassiveDataSocket] 3 sept. 2007 12:15:07.965 : Created passive data-socket: Protocol=Tls1, CompatibilityFlags=SSLDisableControlWaitOnShutdownSSL, UseSSLClosure=True, WaitOnClose=True
DEBUG [FTPControlSocket] 3 sept. 2007 12:15:07.965 : ---> STOR /Anonymous/Azumi.wav
DEBUG [FTPControlSocket] 3 sept. 2007 12:15:07.969 : 150 Opening BINARY mode data connection for /Anonymous/Azumi.wav.
DEBUG [SSLFTPPassiveDataSocket] 3 sept. 2007 12:15:07.970 : Beginning Tls1 handshake on passive data-channel
DEBUG [SocketController] 3 sept. 2007 12:15:07.974 : Processing hello
DEBUG [SSLFTPPassiveDataSocket] 3 sept. 2007 12:15:07.983 : Handshake complete
INFO [FTPClient] 3 sept. 2007 12:16:07.985 : Sending server wakeup message
DEBUG [FTPControlSocket] 3 sept. 2007 12:16:07.985 : ---> NOOP
INFO [FTPClient] 3 sept. 2007 12:17:07.985 : Sending server wakeup message
DEBUG [FTPControlSocket] 3 sept. 2007 12:17:07.985 : ---> NOOP
INFO [FTPClient] 3 sept. 2007 12:18:07.985 : Sending server wakeup message
DEBUG [FTPControlSocket] 3 sept. 2007 12:18:07.985 : ---> NOOP
INFO [FTPClient] 3 sept. 2007 12:19:07.987 : Sending server wakeup message
DEBUG [FTPControlSocket] 3 sept. 2007 12:19:07.987 : ---> NOOP
INFO [FTPClient] 3 sept. 2007 12:20:07.990 : Sending server wakeup message
DEBUG [FTPControlSocket] 3 sept. 2007 12:20:07.990 : ---> NOOP
DEBUG [SSLFTPPassiveDataSocket] 3 sept. 2007 12:21:04.043 : Closing passive data-channel.
DEBUG [SSLFTPPassiveDataSocket] 3 sept. 2007 12:21:04.043 : Beginning SSL closure exchange on passive data-channel.
DEBUG [SSLFTPPassiveDataSocket] 3 sept. 2007 12:21:04.048 : SSL closure exchange
DEBUG [SSLFTPPassiveDataSocket] 3 sept. 2007 12:21:04.048 : Passive data-channel closed
DEBUG [FTPClient] 3 sept. 2007 12:21:04.048 : Transferred 701231104 bytes to remote host
DEBUG [SocketController] 3 sept. 2007 12:21:04.049 : OnReceive closing (socket not connected)
DEBUG [SocketController] 3 sept. 2007 12:21:04.051 : CloseConnection(e=null)
DEBUG [TransferBuffer] 3 sept. 2007 12:21:04.053 : Close() called when open
DEBUG [FTPControlSocket] 3 sept. 2007 12:21:04.054 : 226 Transfer complete. 701231104 bytes transferred. 1969750 Bps.
DEBUG [FTPControlSocket] 3 sept. 2007 12:21:04.108 : ---> PORT 192,168,31,57,207,69
DEBUG [FTPControlSocket] 3 sept. 2007 12:21:04.111 : 200 Command OK.
DEBUG [FTPControlSocket] 3 sept. 2007 12:21:04.111 : ---> RETR /Anonymous

Do you have any hints which could help me to solve this?


Best regards.


Charles

Answer 3

Set the KeepAliveTransfer property to false (the default).

Answer 4

Thanks, that helped.
Now I'm facing forced closure connection from the remote host and resume transfer troubles because of a file watcher, but that is my issue.

Anyway, thanks for your support again.


Charles


Best regards.