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 2003/09/20 08:02:04 UTC
[issues] New comment: (FOR-71) FAQ for memory limits
The following comment has been added to this issue:
Author: David Crossley
Created: Sat, 20 Sep 2003 8:01 AM
Body:
I have made a start on this FAQ. However, i do not understand the remainder of your issue report.
I wonder if this is perhaps a Cocoon issue. It certainly had big build problems at one stage. It should be logged as an issue that needs addressing, rather just as a workaround FAQ.
---------------------------------------------------------------------
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: Unassigned
Priority: Minor
Project: Forrest
Component: Forrest website
Versions:
0.5
Assignee:
Reporter: Dave Brondsema
Created: Thu, 18 Sep 2003 10:28 PM
Updated: Thu, 18 Sep 2003 10:28 PM
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