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 33450] - [net] FTPClient: setSoTimeout() doesn't work properly on retrieveFile() method
Date Fri, 22 Apr 2005 09:15:24 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=33450>.
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=33450





------- Additional Comments From rwinston@eircom.net  2005-04-22 11:15 -------
Actually, I don't believe you are right. setSoTimeout() sets the SO_TIMEOUT
option on the underlying socket, which from the JavaDoc for ServerSocket say:
"With this option set to a non-zero timeout, a read() call on the InputStream
associated with this Socket will block for only this amount of time". As calls
to read() in your situation obviously don't block for longer than the timeout
value (as there is data to read), the timeout will not be triggered.

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