geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-4885) Configure default max heap and max permsize
Date Mon, 19 Oct 2009 19:46:59 GMT

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

Kevan Miller closed GERONIMO-4885.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0

Defaults are now -Xmx 256m and -XX:MaxPermSize=128m.

A default server seems to be using around 80 megabytes of permgen space and 50 megabytes of
heap.

> 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
>            Assignee: Kevan Miller
>             Fix For: 2.2, 3.0
>
>         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.


Mime
View raw message