Using edtFTPj/PRO and getting the following in our logs as a result of an idle connection:
DEBUG (02/24) 15:44:52 [FTPThreadPool]: Calling keepAlive() on stale connection FTPConnection #5
DEBUG (02/24) 15:44:52 [FTPClient]: keepAlive() called
DEBUG (02/24) 15:44:52 [FTPControlSocket]: ---> NOOP
DEBUG (02/24) 15:44:52 [FTPControlSocket]: 200 NOOP Command Successful
WARN (02/24) 15:50:38 [FTPThreadPool]: Idle time has exceeded the maximum (600 s) - disconnecting
DEBUG (02/24) 15:50:38 [FTPControlSocket]: ---> QUIT
DEBUG (02/24) 15:50:38 [FTPControlSocket]: 221 Closing Session
DEBUG (02/24) 15:50:38 [FTPThreadPool]: Exiting FTPKeepAlive thread
INFO (02/24) 15:51:05 [stderr]: com.enterprisedt.net.ftp.FTPException: The file transfer client has not yet connected to the server. The requested action cannot be performed until after a connection has been established.
What is the Idle time being seen here? Is it client-side and, if so, is it configurable? If it is not configurable, what is the best practice for dealing with losing the connection is this manner: a method for checking for a lost connection or catching the exception?
Thanks,
Travis
