Return-Path: 
 <commons-httpclient-dev-return-6950-apmail-jakarta-commons-httpclient-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org
Received: (qmail 72428 invoked from network); 28 Jan 2004 11:14:48 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 28 Jan 2004 11:14:48 -0000
Received: (qmail 41776 invoked by uid 500); 28 Jan 2004 11:03:50 -0000
Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org
Received: (qmail 41755 invoked by uid 500); 28 Jan 2004 11:03:49 -0000
Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Precedence: bulk
List-Unsubscribe: 
 <mailto:commons-httpclient-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-httpclient-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-httpclient-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-httpclient-dev@jakarta.apache.org>
List-Id: "Commons HttpClient Project"
 <commons-httpclient-dev.jakarta.apache.org>
Reply-To: "Commons HttpClient Project"
 <commons-httpclient-dev@jakarta.apache.org>
Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org
Received: (qmail 41654 invoked from network); 28 Jan 2004 11:03:48 -0000
Received: from unknown (HELO rumba.tecnomen.fi) (194.42.63.211)
  by daedalus.apache.org with SMTP; 28 Jan 2004 11:03:48 -0000
Received: (qmail 20694 invoked from network); 28 Jan 2004 09:52:44 -0000
Received: from doormant.tecnomen.fi (194.42.56.206)
  by 0 with SMTP; 28 Jan 2004 09:52:44 -0000
Received: by doormant.tecnomen.fi with Internet Mail Service (5.5.2653.19)
	id <DJXK2K1A>; Wed, 28 Jan 2004 12:03:09 +0200
Message-ID: <BC70F0884912B54E9F65043933CFF5750A719D@aunty.tecnomen.fi>
From: Teemu Tingander <Teemu.Tingander@tecnomen.fi>
To: 'Commons HttpClient Project'
	 <commons-httpclient-dev@jakarta.apache.org>
Subject: RE: Bug in read timout in subsequnt method execution after Connec
	tion: keep-alive [ 2.0_RC3]
Date: Wed, 28 Jan 2004 12:03:08 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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

Yep, if You can do it by my behalf it would be great :)=20

Otherwise I=B4ll have to try to familiarize myself with bugzilla..

- Teemu

-----Original Message-----
From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com]
Sent: 28. tammikuuta 2004 11:35
To: Commons HttpClient Project
Subject: RE: Bug in read timout in subsequnt method execution after
Connection: keep-alive [ 2.0_RC3]


Teemu,
This is the right place, no worries. It appears both 2.0 and HEAD =
exhibit
the reported problem. Do you want me to file a bug report on your =
behalf?
Usually we prefer to have a bugzilla ticket for all known bugs/feature
requests, so the bug resolution audit trail can be retained.

Oleg=20

-----Original Message-----
From: Teemu Tingander [mailto:Teemu.Tingander@tecnomen.fi]
Sent: Tuesday, January 27, 2004 08:15
To: 'commons-httpclient-dev@jakarta.apache.org'
Subject: Bug in read timout in subsequnt method execution after
Connection: keep-alive [ 2.0_RC3]


Hi !

Lets hope that this is right place to mail these issues, Im not =
familiar
with bugzilla so I=B4ll send this to here !=20
Apologies to everyone if this is not..


Changing read timeout ()wont affect after successful method execution =
using
same connection..=20

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
=09
		method.setStrictMode(strictMode);
        		       =20
            if (!connection.isOpen()) {               =20
                connection.setConnectionTimeout(connectionTimeout);
-->		    connection.setSoTimeout(soTimeout);
                connection.open();
                if (connection.isProxied() && connection.isSecure()) {
                    method =3D new ConnectMethod(method);
                }
            }
=20
Problem can be solved by moving the line out of if section

		method.setStrictMode(strictMode);

		connection.setSoTimeout(soTimeout);=09
        		       =20
            if (!connection.isOpen()) {               =20
                connection.setConnectionTimeout(connectionTimeout);
                connection.open();
                if (connection.isProxied() && connection.isSecure()) {
                    method =3D new ConnectMethod(method);
                }
            }

- Teemu

---------------------------------------------------------------------
To unsubscribe, e-mail:
commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
commons-httpclient-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail:
commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
commons-httpclient-dev-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org