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=26500>. 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=26500 New socket timeout value wont have effect if connection is reused Summary: New socket timeout value wont have effect if connection is reused Product: Commons Version: Nightly Builds Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: HttpClient AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Reported by Teemu Tingander <Teemu.Tingander at tecnomen.fi> on The Jakarta Commons HttpClient Developer List: <snip> Changing read timeout ()wont affect after successful method execution using same connection.. This seems to be a bug in HttpClient class method executeMethod(HostConfiguration ...).. The problematic section seems to be if section checking if connection is open method.setStrictMode(strictMode); if (!connection.isOpen()) { connection.setConnectionTimeout(connectionTimeout); --> connection.setSoTimeout(soTimeout); connection.open(); if (connection.isProxied() && connection.isSecure()) { method = new ConnectMethod(method); } } Problem can be solved by moving the line out of if section method.setStrictMode(strictMode); connection.setSoTimeout(soTimeout); if (!connection.isOpen()) { connection.setConnectionTimeout(connectionTimeout); connection.open(); if (connection.isProxied() && connection.isSecure()) { method = new ConnectMethod(method); } } </snip> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
