OutOfMemory Due to Tomcat Memory Leak
Unable to render {include} The included page could not be found.
Symptoms
JIRA crashes after running out of memory. Logs contain the error message OutOfMemory Errors.
Cause
Tomcat 5 caches JSP content. If JIRA is generating huge responses (eg. multi-megabyte Excel or RSS views), then these cached responses will quickly fill up memory and result in OutOfMemoryErrors.
Unable to render {include} The included page could not be found.
Resolution
- In Tomcat 5.5.15+, set the org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true property (see Setting Properties and Options on Startup). This is automatically set in JIRA's stand-alone distributions.
- As a temporary measure, increase JIRA's Heap Space allocation.
- For a more permanent resolution, upgrade Tomcat.
Last modified on Feb 26, 2016
Powered by Confluence and Scroll Viewport.