Socket connect timeout is dependent on the OS.
It is configurable since jdk1.4 through code by creating an unbound
socket and using connect(SocketAddress, timeout)
If one uses java.net.URLConnection there are also:
sun.net.client.defaultConnectTimeout (default: -1)
sun.net.client.defaultReadTime
06, 2003 6:20 PM
To: Commons HttpClient Project
Subject: Re: Timeout in HTTP
Sorry, I misunderstood the question. I agree, it is undefined. It
appears Socket connect timeout is neither documented nor configurable.
My guess is that it's dependent on OS and server response.
Mike
Kalnich
Oleg
-Original Message- From: Michael Becke
[mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2003 16:23 To:
Commons HttpClient Project Subject: Re: Timeout in HTTP
I believe it is being set by HttpClient.execute(). The defaults for
soTimeout and connectionTimeout are both 0.
Mike
Kalnich
constructor would wait indefinitely. Am I missing
something?
Oleg
-Original Message-
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 16:23
To: Commons HttpClient Project
Subject: Re: Timeout in HTTP
I believe it is being set by HttpClient.execute(). The
, June 06, 2003
15:53 To: Commons HttpClient Project Subject: RE: Timeout in HTTP
Yes, that's the point. However, I do not set any value for setTimeout
in HTTPClient. And it is thrown after one minute in average... What's
the default value if nothing is set up ?
-Original Message-
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.
Mike
George Gastaldi wrote:
Hello !
First of all I am new to this list. I have
Hello !
First of all I am new to this list. I have a doubt that seems easy
to answer. What is the default timeout setting value to HTTP Connections ? I
mean, after how many seconds is the HTTPTimeoutException thrown during a GET
operation ?
Thank you !
ifferently? I do not think there's much we can do
about it
Oleg
-Original Message-
From: George Gastaldi [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 15:53
To: Commons HttpClient Project
Subject: RE: Timeout in HTTP
Yes, that's the point. However, I do not set any val
3 10:45 AM
To: Commons HttpClient Project
Subject: RE: Timeout in HTTP
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 confus
: George Gastaldi [mailto:[EMAIL PROTECTED]
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, throw
On Friday, June 6, 2003, at 09:55 PM, George Gastaldi wrote:
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 ?
HttpClient is most likely n
EMAIL PROTECTED]
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
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
13 matches
Mail list logo
