Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-10145

Set tomcat flag to not re-use buffers, as they result in OutOfMemoryErrors

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.7
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently Tomcat re-use their output buffers (ostensibly for performance), but if you serve a large amount of HTML (say 10MB) the buffers sit around forever, and don't get cleaned up. Note that Orion also has this problem.

      There is a flag "org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER" that you can set which limits this. We should set it in the standalone versions, and also let people to know to set it in their own Tomcat instances.

      If you are using Tomcat you must set the following in your java options:

      -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
      

      Note that this option is only available for Tomcat 5.5.15 and above. All earlier Tomcat 5 builds are susceptible to this problem and should be upgraded.

      In JIRA Standalone this is set in the bin/setenv.sh or bin/setenv.bat by default.

      If you do not set this you will get OutOfMemoryErrors.

              Unassigned Unassigned
              scott@atlassian.com Scott Farquhar
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified