OutOfMemory due to Remote API
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
JIRA crashes or behaves unpredictably. Logs contain errors like:
1
java.lang.OutOfMemoryError: Java heap space
Cause
There are two causes:
The SOAP
getProjectscall loads a huge object graph, particularly when there are many users in JIRA, and thus can cause OutOfMemoryErrors. See JRASERVER-10828.A Remote API script that creates an infinite loop, stack overflow, or a highly demanding set of rapid requests can be the culprit.
Diagnosis
To assess which script may be causing performance issues, add access logging and correspond to the out of memory errors.
Resolution
As a temporary measure, increase JIRA's Heap Space allocation.
Ensure no locally run SOAP clients use
getProjects. Use getProjectsNoSchemes instead.Disable or modify scripts as appropriate.
Was this helpful?