nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

API: Downloading attachments >100MB throws com.atlassian.httpclient.api.ResponseTooLargeException

Adam Głębowicz

Hello,

I'm using the official JIRA API client:
jira-rest-java-client-api-5.2.6

I can download attachments from JIRA no problem, BUT if the attachment size is over 100 MB I get an Exception: com.atlassian.httpclient.api.ResponseTooLargeException: Entity content is too long; larger than 104857600 bytes

Is this a client-side or server-side issue?
Where can I change configuration to allow bigger responses than 100 MB?

Regards,
Adam

Accepted answers

Radek Dostál

Should be server-side. At least I think.

If you are a system administrator you can change the maximum allowed attachment size at System>Attachments (/secure/admin/ViewAttachmentSettings.jspa). If it's set to 100MB then that's it.

Technically there isn't really a "hardcap" for max size, but of course generally it is not recommended to be too high because then people start using it as storage and your backup sizes (assuming they include attachments) could grow badly.

All comments

Radek Dostál

Should be server-side. At least I think.

If you are a system administrator you can change the maximum allowed attachment size at System>Attachments (/secure/admin/ViewAttachmentSettings.jspa). If it's set to 100MB then that's it.

Adam Głębowicz

Hello,

The maximum allowed attachment size has always been 800 MB on that JIRA System -> Attachments setting page.
We can upload and download (from the GUI) attachments as big as that.
But we get 100 MB limit issue on the API requests.

Radek Dostál

Yeah it hit me later that it's from the rest client probably and not from Jira (assuming it doesn't "use" Jira settings).

Digging into maven jar repositories there is a hardcoded variable in HttpClientOptions

private long maxEntitySize = 104857600L;

And there is a public setter as well

public void setMaxEntitySize(long maxEntitySize) {
this.maxEntitySize = maxEntitySize;
}

I don't really use this client myself, can you show how you create an instance of the client / what you do before you use it? Then I'm curious if there is a way to set the max entity to a different value if we can get to the HttpClientOptions object. So an actual example how you initialize that client would help me a bit navigating around the jars (the HttpClientOptions is in a pom dependency of that client thing so it's a bit mixed).

I'm not really finding a good documentation for this thing. Lots of different versions, outdated stuff. If you could show what you add to pom and how you use it that'd help to play around with it.

Adam Głębowicz

Hello,

What's the goal here:
I iterate the JIRA IDs I need to migrate and all their Attachments.
I get an inputstream from each attachment and transfer it afterwards to Artifactory as a new attachment (we're moving the attachments).
The part that fails on JIRA side with the limit is highlighted in bold below.

I reference:
jira-rest-java-client-core-5.2.6.jar
jira-rest-java-client-api-5.2.6.jar
and all the compile dependencies for both, including the http libraries you mention.

import com.atlassian.jira.rest.client.api.JiraRestClient;
import com.atlassian.jira.rest.client.api.domain.Attachment;

JiraRestClient jiraClient = AsynchronousJiraRestClientFactory().createWithBasicHttpAuthentication(getJiraUri(JIRA_URL), JIRA_USER, JIRA_PASS);

Iterable<Attachment> jiraItemAttachments = jiraClient.getIssueClient().getIssue(JIRA_ID).claim().getAttachments();

for (Attachment attachment : jiraItemAttachments) {

InputStream attachmentInputStream = null;

URI attachmentUri = null;

try {

attachmentUri = attachment.getContentUri();

attachmentInputStream = jiraClient.getIssueClient().getAttachment(attachmentUri).claim();

} catch (Exception ex) {

System.out.println("Error getting file " + attachment.getFilename() + " / " + ex);

}

(…)

}

If there's a good alternate method of doing the same thing with other API libraries that doesn't face this limit issue, I'd also be happy to use it.

Regards,
Adam

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software-server