Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1333319680.1255461031446.JavaMail.jira@brutus>
Date: Tue, 13 Oct 2009 12:10:31 -0700 (PDT)
From: "Quintin Beukes (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-4885) Configure default max heap and max
 permsize
In-Reply-To: <619794149.1253310736337.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Quintin Beukes updated GERONIMO-4885:
-------------------------------------

    Attachment: default-memory-options.patch

The patch is for both the geronimo.bat and geronimo.sh and sets JAVA_OPTS="-Xmx128m -XX:MaxPermSize=128m" if JAVA_OPTS is empty/unset. Does so after setJavaEnv.bat and setjavaenv.sh has been callled (respectively).

> Configure default max heap and max permsize
> -------------------------------------------
>
>                 Key: GERONIMO-4885
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4885
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.2
>            Reporter: Kevan Miller
>             Fix For: 2.2
>
>         Attachments: default-memory-options.patch
>
>
> It seems that the amount of PermGen space being used by Geronimo 2.2. I think users are more likely to run into OutOfMemoryErrors as a result. Even on small to medium size apps. Setting a default max heap and max perm size should help avoid this...
> Looks like a 2.2 server is using the following:
> 50 MB heap
> 80 MB PermGen
> I'd suggest setting the max for both options to 128M. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.