13

I'm trying to understand the readTimeout available on restTemplate, what is it exactly ?

Is it the the total amount of time the request can take before we get the timeout exception ?

Seb
  • 3,034
  • 8
  • 31
  • 47

3 Answers3

41

As far as i knew, In restTemplate we have 3 type of timeouts

  1. ConnectionRequestTimeout. This is timeout in millis for getting connection from connectionManager

  2. ConnectionTimeout. This is timeout in millis for establishing connection between source and destination

  3. ReadTimeout. This is timeout in millis which expects the response/result should be returned from the destination endpoint.

Dherik
  • 15,440
  • 11
  • 108
  • 148
Dhana
  • 733
  • 1
  • 7
  • 19
  • 2
    This should really be the selected answer as it literally answered the OP's question in a neat way. – AttitudeL Jul 16 '18 at 19:53
  • 9
    ReadTimeout is incorrect, read timeout occurs when time between receiveing two parts of data from server is greater than timeout value. You suggest that it's total time of response, which is not true: total time might be greater than timeout value – wcislo Feb 15 '19 at 10:14
  • 1
    @wcislo is there any way i restrict total time, say 1 min, to receive complete response. – Dhruvam Gupta Feb 09 '20 at 06:21
15

You can define a read timeout on a RestTemplate as follows:

HttpComponentsClientHttpRequestFactory clientRequestFactory = new HttpComponentsClientHttpRequestFactory();
// set the read timeout, this value is in milliseconds
clientRequestFactory.setReadTimeout(500);

RestTemplate restTemplate = new RestTemplate(clientRequestFactory);

Given a readTimeout of X millis, any request made through that RestTemplate instance which takes longer than X millis will result in a ResourceAccessException, wrapping a java.net.SocketTimeoutException with the exception message: "Read timed out".

The timeout is actually implemented by the socket connector inside the HttpClient instance which is wrapped by the RestTemplate so the clock starts when the request first hits that socket and stops when whichever of these comes first: the request completes or the readTimeout is reached.

In effect this means that any request which takes longer than the configured readTimeout will fail with a timeout exception.

Frans
  • 3,163
  • 1
  • 24
  • 23
glytching
  • 40,259
  • 9
  • 100
  • 106
  • Beware that readTimeout doesn't guaratee complete response arrival time limit: [understanding URLConnection.setReadTimeout()](https://stackoverflow.com/questions/24554342/understanding-urlconnection-setreadtimeout) – Vadzim Nov 27 '18 at 21:16
10

You can also define a bean:

@Bean
public RestTemplate restTemplateReadTimeout(RestTemplateBuilder builder) {
    return builder
            .setReadTimeout(15000) //15 seconds
            .build();
}

And use it:

@Autowired
@Qualifier("restTemplateReadTimeout")
private RestTemplate restTemplate;

PS.: When I used this configuration on Spring Boot, I tried to create different RestTemplate Beans with different timeout configurations. But I ended up seeing Spring using always only one timeout configuration (probably using the timeout from the last bean registered), acting as the timeout configuration was a Singleton among the RestTemplates. So pay attention on that, I don't know if was some mistake on my configuration, bug or expected behavior.

Dherik
  • 15,440
  • 11
  • 108
  • 148