forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] New comment: (FOR-71) FAQ for memory limits
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Dave Brondsema
    Created: Tue, 23 Sep 2003 8:38 PM
Well there are 2 sets of factors: OS; and the ant buildfile vs. cocoon.  I have never had
out of memory errors on Windows.  On Solaris, I have had out of memory errors while cocoon
is running.  This is controlled by forrest.maxmemory.  I have also had out of memory errors
when Ant is executing the forrest buildfile (during the copy-content target).  forrest.maxmemory
does not affect this.  To fix it, the forrest and/or ant wrapper scripts, or an environment
variable (like ANT_OPTS) needs to be modified to override the system java vm limit.
View the issue:

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

   Reporter: Dave Brondsema

    Created: Thu, 18 Sep 2003 10:28 PM
    Updated: Thu, 18 Sep 2003 10:28 PM

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  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.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message