Jira is creating temporary files multPartReq
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
Summary
Jira is creating many files with the string name multPartReq* within the directory work/Catalina/localhost/ROOT/
Diagnosis
The origin of these files comes from the class PellMultiPartRequest extends MultiPartRequest and documentation states that this is used for file uploads using a form;
Multipart Form Data request.
This class decodes the multipart/form-data stream sent by an HTML form that uses a file input item.
These tmp files are left behind whenever an attachment is attempted to be added to an incorrect URL.
Below is an example of how to reproduce the issue because the file linked does not exist.
curl -v -D- -u psouza:password -X POST -H "X-Atlassian-Token: no-check" -F "file=@webpack.config.js" http://localhost:8080/jira/browse/BUGTRACK-27If you investigate your Jira logs, you may find stack traces with the following caused by, that may be the origin of the files:
Caused by: org.apache.catalina.connector.ClientAbortException: java.io.EOFException: Unexpected EOF read on the socket
Workaround
These are temporary files that can be safely deleted.
Jira may need to be stopped in order to delete these files because they could be in use by Jira's process.
Solution
Understanding the security concern around the appearance of these unexpected files, we have included a solution into Jira with: JRASERVER-75331 - Getting issue details... STATUS
There is an open feature suggestion to add logging for these files : JRASERVER-73334 - Getting issue details... STATUS