The portal becomes unresponsive due to java.io.IOException: Broken pipe error thrown in the log

Issue

• The portal becomes unresponsive and the log is filled with the below error,

   ERROR [default task-112985][VirtualHostFilter:375] java.io.IOException: Broken pipe
  java.io.IOException: Broken pipe
   at sun.nio.ch.FileDispatcherImpl.writev0(Native Method)
   at sun.nio.ch.SocketDispatcher.writev(SocketDispatcher.java:51)
   at sun.nio.ch.IOUtil.write(IOUtil.java:148)
   at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:504)
   at org.xnio.nio.NioSocketConduit.write(NioSocketConduit.java:161

Environment

• Liferay DXP 7.0, Liferay DXP 7.1, Liferay DXP 7.2, & Liferay DXP 7.3
• Application Server: Tomcat, JBoss EAP 7

Resolution

• The Broken pipe error occurs if Connection between client and server is being broken in amidst of transaction. The most probable root cause in these kinds of issues is related to a network outage.
• Therefore, whenever there are "broken pipe" related errors in logs, check with the network expert to address the network problems.
• To understand in deep the root cause, capture thread dumps at the interval of 5 sec at the time the broken pipe error is thrown in logs. Thread dumps are the most important resource to evaluate the root cause in such scenarios.

Additional Information

• To capture 15-20 thread dumps within the time interval of 5 seconds when the issue has occurred. You can refer the article "Taking Thread Dumps From a JVM".
• To capture the thread dumps, you can also use the scripts attached in the article: How to generate multiple Java Thread Dumps in Linux and Windows
  
• In order to open a performance ticket to the same, refer: Before Opening a Liferay Performance Ticket