Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 73134 invoked from network); 28 Jan 2004 22:00:16 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 28 Jan 2004 22:00:16 -0000 Received: (qmail 34408 invoked by uid 500); 28 Jan 2004 21:59:36 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 34348 invoked by uid 500); 28 Jan 2004 21:59:35 -0000 Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Commons HttpClient Project" Reply-To: "Commons HttpClient Project" Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 34226 invoked from network); 28 Jan 2004 21:59:34 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 28 Jan 2004 21:59:34 -0000 Received: (qmail 14088 invoked by uid 50); 28 Jan 2004 17:59:49 -0000 Date: 28 Jan 2004 17:59:49 -0000 Message-ID: <20040128175949.14087.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-httpclient-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 26500] New: - New socket timeout value wont have effect if connection is reused X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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: commons-httpclient-dev@jakarta.apache.org ReportedBy: olegk@apache.org Reported by Teemu Tingander on The Jakarta Commons HttpClient Developer List: 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); } } --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org