リモート API による OutOfMemory
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
症状
JIRA crashes or behaves unpredictably. Logs contain errors like:
java.lang.OutOfMemoryError: Java heap space
原因
There are two causes:
- The SOAP
getProjects
call 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.
診断
To assess which script may be causing performance issues, add access logging and correspond to the out of memory errors.
ソリューション
- 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.
最終更新日 2022 年 6 月 21 日
Powered by Confluence and Scroll Viewport.