DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31122>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31122
FTPClient deals badly with adverse network conditions
------- Additional Comments From apache@misc.lka.org.lu 2004-09-09 15:25 -------
Some small corrections:
- Problem number 2 and 3 ("hang" if ftp server responds slowly, badly timed
SocketTimeout exceptions) was actually due to an artifact of vsftpd that we
used for testing. Please disregard these item, sorry for the confusion.
However the following point still stands:
1. ftp.isConnected() does not notice that connection has been closed
Additionnally, there are 2 new points:
4. The timeout set by setSoTimeout misfires if the _client_ hasn't submitted a
request for a while. Probably some internal thread is waiting permanently for
server "responses" even if the client didn't send the server anything to
respond to. IMHO, timeout should only be triggered if an _expected_ response
doesn't come.
5. There apparently is no way of setting a timeout for the initial connection
request. Even setDefaultTimeout doesn't work for completely that purpose, as
can be easily checked by attempting to connect to an unreachable IP address.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
|