Getting exception ClientAbortException: java.io.IOException while download large zip file

Question

I am trying to download large zip file from rest API but getting

org.apache.catalina.connector.ClientAbortException: java.io.IOException: connection reset by peer.

Because of connection closed - downloaded zip file is corrupted and I am not able to open it. I tried setting timeout properties but no luck. Also having nginx api gateway configuration also for the service.

This is the stacktrace:

org.apache.catalina.connector.ClientAbortException: java.io.IOException: Connection reset by peer
    at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:351) ~[tomcat-embed-core-9.0.38.jar!/:9.0.38]
    at org.apache.catalina.connector.OutputBuffer.flushByteBuffer(OutputBuffer.java:776) ~[tomcat-embed-core-9.0.38.jar!/:9.0.38]
    at org.apache.catalina.connector.OutputBuffer.append(OutputBuffer.java:681) ~[tomcat-embed-core-9.0.38.jar!/:9.0.38]
    at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:386) ~[tomcat-embed-core-9.0.38.jar!/:9.0.38]
    at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:364) ~[tomcat-embed-core-9.0.38.jar!/:9.0.38]
    at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:96) ~[tomcat-embed-core-9.0.38.jar!/:9.0.38]
    at org.springframework.util.StreamUtils.copy(StreamUtils.java:166) ~[spring-core-5.2.9.RELEASE.jar!/:5.2.9.RELEASE]
    at org.springframework.http.converter.ResourceHttpMessageConverter.writeContent(ResourceHttpMessageConverter.java:137) ~[spring-web-5.2.9.RELEASE.jar!/:5.2.9.RELEASE]
    at org.springframework.http.converter.ResourceHttpMessageConverter.writeInternal(ResourceHttpMessageConverter.java:129) ~[spring-web-5.2.9.RELEASE.jar!/:5.2.9.RELEASE]
    at org.springframework.http.converter.ResourceHttpMessageConverter.writeInternal(ResourceHttpMessageConverter.java:45) ~[spring-web-5.2.9.RELEASE.jar!/:5.2.9.RELEASE]
    at org.springframework.http.converter.AbstractHttpMessageConverter.write(AbstractHttpMessageConverter.java:227) ~[spring-web-5.2.9.RELEASE.jar!/:5.2.9.RELEASE]
    at org.springframework.web.servlet.mvc.method.annotation.AbstractMessageConverterMethodProcessor.writeWithMessageConverters(AbstractMessageConverterMethodProcessor.java:280) ~[spring-webmvc-5.2.9.RELEASE.jar!/:5.2.9.RELEASE]
    at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.h

Configuration file:

server:
  connection-timeout: -1
  tomcat :
    async-timeout: 60000
    connectTimeout: 60000
    requestTimeout: 60000
    socketTimeout: 60000

This is Spring with Tomcat embedded server version 9.0.38.

I’d check your Nginx configuration. “Connection reset by peer” indicates that whatever Tomcat was talking to has closed the connection. — Andy Wilkinson, May 22 '21 at 06:30
nginx.ingress.kubernetes.io/proxy-connect-timeout: "180" nginx.ingress.kubernetes.io/proxy-read-timeout: "600" nginx.ingress.kubernetes.io/proxy-send-timeout: "180" having this configuration for nginx. and using postman to download the file and also increased request timeout at postman. — govind, May 22 '21 at 07:45

score 0 · Answer 1 · answered May 22 '21 at 06:37

Cause This exception happens when the Tomcat server tries to write back response to the client but it finds that the connection has been closed from the client side. It could happen in the following situations from the client side before the server completes the request: Web browser is closed Web page is refreshed or navigated away HTTP client closes the connection due to a socket timeout happens from client side

Solution Check the behavior or HTTP request invocation code of the web clients(Browser or REST client) from client side, find out if any of the above situations happen. If in some heavy load situation like too many concurrent requests hit the Historian Tomcat server intensively, the server may take too long to complete the requested operation, causing timeout occurs from the client side and connection gets closed by the client before the server writes the response. In this situation, user can consider increasing the socket timeout value for the HTTP Client, take the below sample Java code which sets the time out values for the HttpClient as a reference:

DefaultHttpClient httpClient = new DefaultHttpClient();
HttpParams params = httpClient.getParams();
HttpConnectionParams.setConnectionTimeout(params, connectionTimeoutMillis);
HttpConnectionParams.setSoTimeout(params, socketTimeoutMillis);

wish I was helpful.

score 0 · Answer 2 · answered May 22 '21 at 08:06

Your log indicates ClientAbortException, which occurs when your HTTP client drops the connection with the server and this happened before the server could close the server socket Connection. Also, it might your HTTP client disconnected.

This could have a couple of reasons:

Responding to the request took too long, the client gave up
You responded with something the client did not understand
The end-user actually canceled the request
A network error occurred
... probably more

You can fairly easily emulate the behavior:

URL url = new URL("http://example.com/path/to/the/file");

int numberOfBytesToRead = 200;

byte[] buffer = new byte[numberOfBytesToRead];
int numberOfBytesRead = url.openStream().read(buffer);

zip file size aprox 80Mb. So it will take time to download. that why nginx.proxy_read_out: "600". So this should not be case. event i increased readtimeout for postman also. logs clearly says connection is aboted by tomcat server. so not sure what going on. is there any way to customize Tomcat Connector properties? — govind, May 22 '21 at 09:40

Getting exception ClientAbortException: java.io.IOException while download large zip file

2 Answers2