commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35777] - [net] FTPClient.connect() does not timeout
Date Mon, 18 Jul 2005 21:59:25 GMT
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=35777>.
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=35777





------- Additional Comments From dfs@apache.org  2005-07-18 23:59 -------
(In reply to comment #1)
> Looking through the (1.4.0) code, I can't see setSoTimeout() being called on 
> the control connection, only on the data connections. Could this be the cause 
> of the problem?

setSoTimeout affects only I/O operations on an established connection.  It
doesn't affect connection establishment.  You can work around the issue with
the SocketFactory as described in Comment #2, but the ultimate solution for
this and other issues is to implement a Commons Net 2.0 that abandons
compatibility with legacy Java releases and perhaps even abandons
compatibility with Commons Net 1.x.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message