ClientAbortException java.net.SocketException broken pipe
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The following error appears in the logs:
WARNING: Exception Processing ErrorPage[errorCode=500, location=/500page.jsp]
ClientAbortException: java.net.SocketException: Broken pipe
WARNING: Exception Processing ErrorPage[errorCode=404, location=/fourohfour.action]
ClientAbortException: java.net.SocketException: Broken pipe
Cause
The warning log basically means that the connection to the client browser is aborted before the response is fully transferred. It is a harmless warning as it can be due to transient network problems or the browser aborts/refreshes the page before it loaded.
This error is also known to affect image files in TIF format. Specifically, this error is thrown when browsing the page using Internet Explorer.
Resolution
See also "Communications link failure" Error with JIRA User Management on MySQL. If the problem is not the database connection as described in that article, you may choose to do nothing. If you're getting a lot of these, it might be a sign of a performance problem.