You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2004/04/27 00:08:47 UTC
[issues] Updated: (FOR-71) FAQ for memory limits
The following issue has been updated:
Updater: Juan Jose Pablos (mailto:cheche@che-che.com)
Date: Tue, 27 Apr 2004 12:08 AM
Changes:
[Fix For] set to [0.6]
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-71&page=history
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-71
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-71
Summary: FAQ for memory limits
Type: Improvement
Status: Assigned
Priority: Minor
Project: Forrest
Component: Forrest website
Fix For: 0.6
Versions:
0.5
Assignee: Dave Brondsema
Reporter: Dave Brondsema
Created: Thu, 18 Sep 2003 10:28 PM
Updated: Tue, 27 Apr 2004 12:08 AM
Description:
There should be an FAQ for "out of memory" errors. I don't know about running as a webapp, but the following applies to the CLI. The first suggestion would be to set forrest.maxmemory in forrest.properties. However, this only affects Cocoon; if the out of memory error happens in copy-content or any other part of the ant buildfile, the $ANT_OPTS env var should be set to the appropriate Java VM options. That of course is only specific to linux/unix. I've never had memory problems in Windows though.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org/jira//Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira