Why Your Java HTTP Client Hangs for 15 Minutes and How to Fix It

Introduction

In many backend systems, asynchronous calls to third‑party services are performed via a message queue. The author experienced a situation where the queue became blocked for more than ten minutes, causing downstream messages to stop processing.

Problem Symptoms

The queue appeared to be stuck: messages piled up, and no new messages could be added. Logs showed that a producer had posted data once and then stopped, while the consumer continued processing for several minutes after that, indicating that the producer was being blocked by the consumer.

Investigation Steps

The author first considered the queue implementation itself (e.g., a while‑true loop with sleep) and ruled out excessive sleep or thread interruption. By examining logs, it became clear that the consumer’s HTTP request was holding the connection for an unusually long time.

Root Cause

Log analysis revealed an HTTP request whose parameters were logged, but the response was only logged after a 15‑minute delay, showing a remote service exception. The underlying code used Apache HttpClient without any timeout settings, causing the request to wait indefinitely.

public static String doPostWithJSON(String url, String json) throws Exception {
    CloseableHttpClient client = HttpClients.createDefault();
    HttpPost httpPost = new HttpPost(url);
    httpPost.setHeader("Content-Type", "application/json;charset=UTF-8");
    StringEntity se = new StringEntity(json, Charset.forName("UTF-8"));
    se.setContentType("application/json");
    httpPost.setEntity(se);
    CloseableHttpResponse response = client.execute(httpPost);
    HttpEntity entity = response.getEntity();
    String result = EntityUtils.toString(entity, "UTF-8");
    return result;
}

Because no timeout was configured, the client waited until the remote service finally timed out after fifteen minutes.

Setting Timeouts in Different HttpClient Versions

HttpClient 4.3 :

httpClient.getParams().setParameter(CoreConnectionPNames.CONNECTION_TIMEOUT, 10000);
httpClient.getParams().setParameter(CoreConnectionPNames.SO_TIMEOUT, 10000);

HttpClient 4.4 and later :

RequestConfig requestConfig = RequestConfig.custom()
    .setSocketTimeout(10000)
    .setConnectTimeout(10000)
    .build();
httpGet.setConfig(requestConfig);

setConnectTimeout

defines the maximum time to establish a connection (milliseconds), while setSocketTimeout defines the maximum period of inactivity between data packets. If the remote service does not respond within these limits, the request is aborted and an exception is thrown.

Conclusion

The case demonstrates how a missing timeout configuration in an HTTP client can silently block a production system. Setting appropriate connection and socket timeouts for every HTTP call, and handling the resulting exceptions, is essential to avoid similar incidents.