hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Teemu Tingander <Teemu.Tingan...@tecnomen.fi>
Subject RE: Bug in read timout in subsequnt method execution after Connec tion: keep-alive [ 2.0_RC3]
Date Wed, 28 Jan 2004 10:03:08 GMT
Yep, if You can do it by my behalf it would be great :) 

Otherwise I´ll 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 

-----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´ll send this to here ! 
Apologies to everyone if this is not..


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);
                }
            }

- 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


Mime
View raw message