Return-Path: Delivered-To: apmail-jakarta-httpclient-user-archive@www.apache.org Received: (qmail 8712 invoked from network); 11 Oct 2005 09:09:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Oct 2005 09:09:54 -0000 Received: (qmail 50774 invoked by uid 500); 11 Oct 2005 09:09:54 -0000 Delivered-To: apmail-jakarta-httpclient-user-archive@jakarta.apache.org Received: (qmail 50762 invoked by uid 500); 11 Oct 2005 09:09:54 -0000 Mailing-List: contact httpclient-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: "HttpClient User Discussion" Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-user@jakarta.apache.org Received: (qmail 50751 invoked by uid 99); 11 Oct 2005 09:09:54 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Oct 2005 02:09:54 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [80.74.144.174] (HELO uml24.umlhosting.ch) (80.74.144.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Oct 2005 02:09:56 -0700 Received: from oleg by uml24.umlhosting.ch with local (Exim 4.50) id 1EPG8Z-00085X-AY for httpclient-user@jakarta.apache.org; Tue, 11 Oct 2005 11:09:31 +0200 Date: Tue, 11 Oct 2005 11:09:31 +0200 From: Oleg Kalnichevski To: httpclient-user@jakarta.apache.org Subject: Re: Socket management Message-ID: <20051011090931.GA31081@uml24.umlhosting.ch> Mail-Followup-To: httpclient-user@jakarta.apache.org References: <687B7858C99ED711B87B00B0D0D1C922030A5490@lambic.guideworks.tv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <687B7858C99ED711B87B00B0D0D1C922030A5490@lambic.guideworks.tv> User-Agent: Mutt/1.5.9i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Mon, Oct 10, 2005 at 11:33:33AM -0600, Steven Terrell wrote: > I am using HttpClient 3.0 RC3 to talk to a servlet on Tomcat (5.5.9 I > think.) My application is using the MultiThreadedConnectionManager. There is > a 5 second timeout for each request made to Tomcat. My code calls > PostMethod.releaseConnection in the finally clause, as the examples do. I am > interested in understanding what happens with the socket (client and server > side) when that timeout value is reached. Particularly, what happens if the > Tomcat servlet still tries to send a response even though I have timed out? > > Steven, I believe a socket timeout exception will leave the socket in pending close state, thus rendering it unusable for any further I/O operations. HttpClient will always close the connection, which threw an IOException (such as SocketTimeoutException). The server socket in its turn will end up throwing a SocketException: "Software caused connection abort: socket write error" as a result of this Oleg > > If there is a good link I can follow to answer this question, please post > it! Thanks, > > > > Steve Terrell > > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-user-help@jakarta.apache.org