This article mentions the steps for overcoming errors while exporting data to Excel from Worklogs Report on Server/Data Center. These errors are infrequent and often arises in non-default Jira configurations or with extensive reports containing 5,000+ issues.
The problem can potentially be resolved by adjusting the POST size, which governs the maximum file size for downloads.
It is crucial to exercise caution when modifying these settings, as improper changes can lead to severe consequences, such as server failures and data loss.
Therefore, we strongly recommend that only skilled administrators, well-versed in Jira's configuration and underlying infrastructure, handle such modifications.
What directories and files should you consider?
Before proceeding with the steps below, please refer to the following Atlassian article to learn how to locate installation directories and configuration files.
How can you increase the Jira Server POST size?
The default value for the POST size in the Tomcat server, which Jira utilizes, is set at 2,097,152 bytes (2MB). This limit can be increased further.
-
To increase this limit, you will need to modify the
server.xmlfile within Jira's configuration.For example, in the default Linux distribution, you can find this file in the
/opt/atlassian/jira/conffolder. -
In the
Connectorsection, add themaxPostSizeattribute with an appropriately large value, such as 10485760, which corresponds to 10MB. This should be sufficient for generating a report with 10,000 issues.For example:
<Connector port="8080" ... maxPostSize="10485760"/>
See more: Apache Tomcat 8 Configuration Reference.
How can you increase the POST limit size on the reverse proxy server?
It may be required to increase the POST limit size in the reverse proxy server.
You can use a property called client_max_body_size in a NGINX server for this purpose.
server {
listen 443 ssl;
client_max_body_size 10M;
location / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_read_timeout 300s;
proxy_pass http://localhost:8080;
}
}
See more: NGINX Module ngx_http_core_module.
If you have questions or need assistance, contact our support team via email or service desk. Our team is available Monday through Friday (9:00 AM to 7:00 PM GMT+7) to help with technical challenges or discuss improvements.