connect.timeout and io.timeout -query

Google Cloud Apigee
1

As io.timeout is the timeout set to receive response from backend ,and connect.timeout is the timeout set to establish connection with backend,I believe connect.timeout should be very much lesser than io.timeout.

As per my understanding,io.timeout can be little higher than the maximum response SLA of backend.If backend max response SLA is 1 minute,we can set io.timeout as 65s ,while connect.timeout can be set as 5000ms.

But I am not sure why they both are given same values in apigee docs posted in http://studylib.net/doc/7018421/api-proxy-documentation link.

<HTTPTargetConnection>
<Properties>
<Property name="connect.timeout.millis">30000</Property>
<Property name="io.time
out.millis">30000</Property>
</Properties>
<URL>http://www.apigee.com</URL>
</HTTPTargetConnection>

I would like to understand the reason behind applying same timeout milliseconds for both connect.timeout and io.timeout.Please help me understand this and how we should usually set.

2

They are just sample values. In general, io.timeout should be higher than the connect.timeout

1 Like
3

Hi @Subbu R,

Please find the following differences

Property Name Default Value Description
connect.timeout.millis 3000 Target connection timeout. Edge returns an HTTP 503 status code if a connection timeout occurs.
io.timeout.millis 120000 If there is no data to read for the specified number of milliseconds, or if the socket is not ready to write data for specified number of milliseconds, then the transaction is treated as a timeout.
- If a timeout happens while reading HTTP request, 408,RequestTimeout is returned.
- If a timeout happens while reading HTTP response, 504,GatewayTimeoutis returned.

Refer to Endpoint Properties Reference

4

Thanks @Sathish Balasubramaniyan .This helps..

5

@Subbu R, @Sathish Balasubramaniyan @Aswin Segu

Is their any way to dynamically set these properties per environment using KVM : will that work ?

3000

3000