Why Your HttpClient Throws SocketClosed and How Reordering the Close Fixes It

When using Apache HttpClient for API testing, the author repeatedly encountered a SocketClosed exception. Initial investigation blamed request.releaseConnection(), but the real cause was the premature closing of the CloseableHttpResponse object.

Because the response body can be large, calling EntityUtils.toString(entity) may fail if the underlying entity has not been fully read before response.close() is invoked. The close operation aborts the stream, leading to the socket being closed unexpectedly.

Original code snippet

try {
    response.close();
} catch (IOException e2) {
    output("响应关闭失败！", e2);
}

data_size = entity.getContentLength(); // 获取相应数据大小
if (data_size == -1) { // 如果为-1，则重置data_size
    data_size = 0;
}
String content = null;
try {
    content = EntityUtils.toString(entity); // 用string接收响应实体
    EntityUtils.consume(entity); // 消耗响应实体
} catch (ParseException e1) {
    output("解析响应实体异常！", e1);
} catch (IOException e1) {
    output("解析响应实体时java IO 异常！", e1);
}
// 解析响应

In this version, response.close() is called before the entity is fully consumed, which can trigger the socket error.

Modified code snippet

String content = null;
try {
    content = EntityUtils.toString(entity); // 用string接收响应实体
    EntityUtils.consume(entity); // 消耗响应实体
} catch (ParseException e1) {
    output("解析响应实体异常！", e1);
} catch (IOException e1) {
    output("解析响应实体时java IO 异常！", e1);
}
// 解析响应
try {
    response.close();
} catch (IOException e2) {
    output("响应关闭失败！", e2);
}

By moving the response.close() call to the end—after EntityUtils.consume(entity) —the socket remains open long enough for the entity to be fully read, eliminating the SocketClosed error.

Key takeaways:

Never close the HttpResponse before fully consuming the response entity.

Use EntityUtils.consume(entity) or read the stream completely before invoking close().

This adjustment works even when the response payload is large.