You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by "David Crossley (JIRA)" <ji...@apache.org> on 2006/03/27 06:08:26 UTC

[jira] Updated: (FOR-591) MaxMemory needs increasing

     [ http://issues.apache.org/jira/browse/FOR-591?page=all ]

David Crossley updated FOR-591:
-------------------------------

    Urgency: Urgent
    Version: 0.7

Setting Urgency=urgent. This issue was already present in the 0.7 release, so it probably isn't a blocker. It became apparent due to our hefty site-author docs arrangement, so it is a blocker for that situation. It would certainly be good to have fixed.

> MaxMemory needs increasing
> --------------------------
>
>          Key: FOR-591
>          URL: http://issues.apache.org/jira/browse/FOR-591
>      Project: Forrest
>         Type: Bug
>   Components: Core operations
>     Versions: 0.8-dev, 0.7
>     Reporter: Ross Gardler
>     Priority: Blocker
>      Fix For: 0.8-dev

>
> Since the docs restructurng for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site.
> Does this indicate a memory leak?
> Does someone have the tools to run some diagnostics?
> (NB maxmemory has been increased in forrest.properties, if we resolve this issue it should be reduced again)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira