History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-10145
Type: Task Task
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Scott Farquhar [Atlassian]
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

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

Created: 11/May/06 08:01 PM   Updated: 02/Oct/07 09:47 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 3.7

Time Tracking:
Original Estimate: 4 hours
Original Estimate - 4 hours
Remaining Estimate: 4 hours
Remaining Estimate - 4 hours
Time Spent: Not Specified
Remaining Estimate - 4 hours

Issue Links:
Duplicate
 
Reference
 

Participants: Jed Wesley-Smith [Atlassian] and Scott Farquhar [Atlassian]
Since last comment: 32 weeks, 2 days ago
Resolution Date: 16/May/06 09:23 PM
Labels:


 Description  « Hide
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.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order

Scott Farquhar [Atlassian] - 16/May/06 08:55 PM
More information about setting JVM options can be found in this knowledge base article:

http://confluence.atlassian.com/display/JIRA/Setting+properties+and+options+on+startup


Jed Wesley-Smith [Atlassian] - 02/Oct/07 09:47 PM
JIRA v3.11.1 and above now checks the Tomcat version and logs an error at start-up if this is not set.