DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23746>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23746 SocketClient.setDefaultTimeout has no effect [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-10-12 06:18 ------- This report is invalid. The documentation refers to the API user calling connect, not how the API is implemented to achieve its documented effects. setDefaultTimeout() does exactly what it claims to do. That is, if you call setDefaultTimeout() after calling connect(), it will have no effect. It is a "default" timeout value that is automatically set for the API user. As the documentation states, it is not to be confused with setSoTimeout(), which the issue reporter appears to have done. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
