hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kalnichevski, Oleg" <oleg.kalnichev...@bearingpoint.com>
Subject RE: Timeout in HTTP
Date Fri, 06 Jun 2003 13:44:44 GMT
George,

Please note that HttpConnection.ConnectionTimeoutException represents a connection timeout
(set with HttpClient#setConnectionTimeout), not a read timeout (set with HttpClient#setTimeout).
Can it be that this confusion is the source of the problem?

Oleg

-----Original Message-----
From: George Gastaldi [mailto:george.gastaldi@neogrid.com.br]
Sent: Friday, June 06, 2003 13:55
To: Commons HttpClient Project
Subject: RE: Timeout in HTTP


	That's strange, because even when I do not set anything, the
connection times out for about 1 minute, throwing a
HttpConnection.ConnectionTimeoutException. Setting explicitly to 0 will
never timeout ? 

Thank you for the answer.

-----Original Message-----
From: Ortwin Gl├╝ck [mailto:ortwin.glueck@nose.ch]
Sent: Friday, June 06, 2003 3:26 AM
To: Commons HttpClient Project
Subject: Re: Timeout in HTTP


Michael Becke wrote:
> I am assuming you are talking about SO_TIMEOUT set via 
> HttpClient.setTimeout().  This is the amount of time to wait when 
> reading on an open socket.  This defaults to 0 which means that it will 
> wait forever.

"forever" means "until the server is bored and closes the connection" :-)


---------------------------------------------------------------------
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