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 ?
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 ?
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.
As far as i knew, In restTemplate we have 3 type of timeouts
ConnectionRequestTimeout. This is timeout in millis for getting connection from connectionManager
ConnectionTimeout. This is timeout in millis for establishing connection between source and destination
ReadTimeout. This is timeout in millis which expects the response/result should be returned from the destination endpoint.
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.
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.
I know this isn't the OP question, but I suspect a lot of people (like myself) end up here trying to find how to set the read timeout, not just what it is.
The existing 2 code examples no longer work in Spring Boot 3 / Spring Framework 6, so this was the easiest I found:
// Using the builder pattern
restTemplate = new RestTemplateBuilder().setReadTimeout(Duration.ofSeconds(10)).build();
It is technically still possible to configure the connection factory directly, but it's a bit more verbose than it was in prior Spring versions:
To change the socket read timeout, use SocketConfig.Builder.setSoTimeout(Timeout), supply the resulting SocketConfig to org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManagerBuilder.setDefaultSocketConfig(SocketConfig), use the resulting connection manager for org.apache.hc.client5.http.impl.classic.HttpClientBuilder.setConnectionManager(HttpClientConnectionManager), and supply the built HttpClient to HttpComponentsClientHttpRequestFactory(HttpClient).
© 2022 - 2025 — McMap. All rights reserved.