java.net.SocketException: Connection reset

[former_member732579]

We have a lot of errors on the Production environment on all nodes, especially on front-end nodes.

From the stack trace, it's not possible to determine what call is causing an issue. Any suggestions?

Below is a count of errors thought one day

[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hyapp1/hybris/tomcat/console-20210902.log | wc -l
293
[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hyapp2/hybris/tomcat/console-20210902.log | wc -l
255
[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hyapp3/hybris/tomcat/console-20210902.log  | wc -l
262
[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hysvc1/hybris/tomcat/console-20210902.log | wc -l
3
[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hysvc2/hybris/tomcat/console-20210902.log | wc -l
4
[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hysvc3/hybris/tomcat/console-20210902.log | wc -l
2
[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hysvc4/hybris/tomcat/console-20210902.log | wc -l
1
[prodlog@btl-hylog01 prod]$ zgrep -iaH 'org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset' ./bpl-hysvc5/hybris/tomcat/console-20210902.log | wc -l
2

Part of logs that shows the frequency of reset connections:

connectionresethybrisstacktrace.txt

connectionresethybrisstacktrace.txt

[sserafimov]

Hi Pavel,

From the provided log it's not clear what is causing it.

If you review your integrations and run it from the server where the code has been deployed. I am sure that you will find the answer.

BR,