Starting JIRA Produces an Error about the Limit Buffer

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

Every time JIRA starts the following error appears in the logs:

WARNING: 'Apache Tomcat/6.0.20' server and the 'org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER' system property is not set to true! This can result in OutOfMemoryErrors. For more information please see [http://www.atlassian.com/software/jira/docs/latest/servers/tomcat60.html].

Cause

The message appears as JIRA requires that you set the LIMIT_BUFFER to be true, so as to prevent Tomcat from leaking memory by caching JSPs, as in JRA-10145 - Getting issue details... STATUS . This can also occur if there is an extra space after the true parameter.

Resolution

  1. As in our Setting Properties and Options on Startup, set the below JVM argument:

    -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
  2. If the parameter is set, make sure that there is not a space at the end of -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true parameter.
Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.