Downloading Attachments Results in java.net.SocketException Connection Reset
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Symptoms
Downloading attachments fails displaying the error in the JIRA logs:
1
2
3
4
5
6
7
8
9
10
11
12
13
2007-07-13 14:31:15,851 TP-Processor1 ERROR [jira.web.servlet.ViewAttachmentServlet] Error finding /10015/screenshot-2.jpg: null
ClientAbortException: java.net.SocketException: Connection reset
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
....
Caused by: java.net.SocketException: Connection reset
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
at org.apache.jk.common.JkInputStream.doWrite(JkInputStream.java:147)
at org.apache.coyote.Response.doWrite(Response.java:559)
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:361)
... 50 more
Cause
There are four possibilities that could be causing this error:
The firewall may have been configured incorrectly ultimately rejecting the attachment.
There is a flaky connection while accessing JIRA.
The attachments directory may have been moved.
User has closed their browser in the midst of viewing an attachment
Resolution
Check system's firewall settings to make sure that JIRA has access to add the attachments.
Ensure that there is no packet loss or dropped connections. A good tool to test this with would be WireShark.
Check to make sure that the attachments directory is configured correctly.
Was this helpful?