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 Tue, 19 Jul 2005 19:20:11 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


dfs@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From dfs@apache.org  2005-07-19 21:20 -------
Alright, if it's the socket timeout, then there's no problem.
I thought you were referring to the connect because of:

>that FTPClient.connect() had been called but had not returned.

and

>Summary: [net] FTPClient.connect() does not timeout

SocketClient.setDefaultTimeout sets the default timeout value that will
be set immediately after connection establishment.  As the documentation
says, it only has effect if called prior to connecting and should
not be confused with SocketClient.setSoTimeout.  At worst, the wording
may be unclear, but I don't think it's incorrect.  I'll see about
clarifying it.  Using setDefaultTimeout is not a workaround.  It's
the correct/standard procedure :)  You can also set the data
connection timeout with FTPClient.setDataTimeout.  setDefaultTimeout affects
only the control connection.

>Secondly, When connect() establishes a TCP connection but subsequently fails, 
>it does not close the socket.

If connect() establishes a TCP connection, then there is no failure.  If
an error occurs, an IOException will be thrown.  It is the API user's
responsibility to catch the exception and close the connection if already
established.

It sounds like there's no issue here, so I'm changing the resolution to
INVALID.  I think this issue, like some others, is really indicative of
the need for a programmer's guide (beyond mere javadocs), but I don't
see the time/resources/volunteers materializing for such :(

-- 
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