Difference between 'Read timeout' & 'Response timeout' & 'Connecttimeout'

[Eddieturbo]

Hi,

Can anyone tell me exactly what the difference is between a 'Read
timeout' & 'Response timeout' & 'Connect timeout'?

Thanks,

Eddie

 

[Arne Vajhøj]

Can anyone tell me exactly what the difference is between a 'Read
timeout' & 'Response timeout' & 'Connect timeout'?

It is difficult to give exact definitions without context.

General I will say:

connect timeout = attempt to connect did not succeed before limit

read timeout = response timeout = no data received before limit

Arne

 

[EJP]

Can anyone tell me exactly what the difference is between a 'Read
timeout' & 'Response timeout' & 'Connect timeout'?

Connect timeout and read timeout have already been covered. A response
timeout is a read timeout when what you trying to read is a response.

 

[Arne Vajhøj]

Connect timeout and read timeout have already been covered. A response
timeout is a read timeout when what you trying to read is a response.

And at least in some contexts responses are read and
requests are written.

Arne

 

[Eddieturbo]

Thanks for all the replies.

Yes, point taken Arne. So here goes:

SUN One Application Server running an Application which uses
apache.commons.httpclient to make connections to an Application
running in a WebSphere Application Server v5.1 instance.

the httpclient has the following settings:

connect_timeout = 5000 (ms)
response_timeout = 2500 (ms)

However it looks like neither is timeout works when we get a "Read
timeout" errors in the logs.

So it would appears that they are actually different.

I can understand the connect_timeout but I don't am not able to see
the difference between a response timeout and a read timeout in this
context.

Thanks,

EddieT

 

[EJP]

response_timeout = 2500 (ms)

That's pretty short. I'd set it to at least 10 seconds.

So it would appears that they are actually different.

Yes, that's what we said.

I can understand the connect_timeout but I don't am not able to see
the difference between a response timeout and a read timeout in this
context.

There isn't one. See the previous answers. This is an HTTPClient, which
is a client, which writes requests and reads responses, so a response
timeout is a read timeout.

 

[Arne Vajhøj]

That's pretty short. I'd set it to at least 10 seconds.

I think that should depend on the context (network and expected
processing time in the remote end).

2.5 seconds is forever in some contexts.

Arne

 

[Arne Vajhøj]

So here goes:

SUN One Application Server running an Application which uses
apache.commons.httpclient to make connections to an Application
running in a WebSphere Application Server v5.1 instance.

Isn't that a scenario where web service calls would make sense?

the httpclient has the following settings:

connect_timeout = 5000 (ms)
response_timeout = 2500 (ms)

However it looks like neither is timeout works when we get a "Read
timeout" errors in the logs.

So it would appears that they are actually different.

I can understand the connect_timeout but I don't am not able to see
the difference between a response timeout and a read timeout in this
context.

I can not see those in:
http://hc.apache.org/httpclient-3.x/preference-api.html

Arne