geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <>
Subject [jira] Updated: (GERONIMO-3838) memory (probably related to sessions) leak
Date Fri, 19 Sep 2008 06:54:44 GMT


Ivan updated GERONIMO-3838:

    Attachment: Geronimo-3838-TomcatWebAppContext.patch

    I divided the patch for two files.  The one Geronimo-3838-ManagerGBean.patch is to make
ManagerGBean to support PersistenceManager configuration. And the other one is I am not quite
sure. If I write <ManagerRetriever>TomcatManager</ManagerRetriever> in the plan
file, it says that Manager element is expected, but if I write <Manager>TomcatManager</Manager>,
it would say that no reference name "Manager" is found. Could anyone give some comments, for
I found WADITomcatClusteringBuilder has reference to that static string. Thanks !

> memory (probably related to sessions) leak
> ------------------------------------------
>                 Key: GERONIMO-3838
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Memory Leaks, Tomcat
>    Affects Versions: 2.0.2, 2.1.1
>         Environment: tested with JDK 1.5 running on Windows XP and FreeBSD6.2
>            Reporter: Radim Kolar
>            Priority: Critical
>             Fix For: 2.2
>         Attachments: Geronimo-3838-ManagerGBean.patch, Geronimo-3838-TomcatWebAppContext.patch
> There is memory leak and it can be repeated very easily, so it should be very easy to
> Install Geronimo and then run some kind of benchmarking software against its admin UI
login page, for example
> program ab from Apache HTTP. This is realistic attack scenario, because lot of denial
of service attacks are doing this (requesting one page many times).
> Watching memory used graph in admin console shows free memory slowly decreasing. After
all available memory is exhausted, application server stops serving new requests and never
restores ifself back to working state.
> I think that it is caused by allocating sessions without limiting total number of sessions
to keep in memory and possibly to swap sessions out to file. There needs to be user-configurable
setting for preventing this, it would be nice to add such setting to Admin console.
> Its very important to get this bug fixed.

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

View raw message