Return-Path: Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 86042 invoked from network); 15 Apr 2003 07:28:16 -0000 Received: from unknown (HELO nose.ch) (195.134.131.71) by daedalus.apache.org with SMTP; 15 Apr 2003 07:28:16 -0000 Received: (qmail 12025 invoked from network); 15 Apr 2003 08:28:15 -0000 Received: from calvin.nose.ch (HELO nose.ch) (192.168.1.7) by 0 with SMTP; 15 Apr 2003 08:28:15 -0000 Message-ID: <3E9BB491.2020705@nose.ch> Date: Tue, 15 Apr 2003 09:28:17 +0200 From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: de-ch, en-us MIME-Version: 1.0 To: Commons HttpClient Project Subject: Re: Still problems with HttpRecoverableException and HTTPS References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Adrian Sutton wrote: > Okay, in that case I'm putting my money on finding something like the > following in the server code: > > if (timeoutShouldHappenNow) { > outputStream.close(); > } > > In other words, it closes the output stream but not the input stream or > something similar. Possibly a bug in the JVM that causes socket.close() > to only close the output stream or something as well. That is generally called a "half-open socket". While legitimate, it's not ideal in this situation...