struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maurizio Cucchiara (Commented) (JIRA)" <>
Subject [jira] [Commented] (WW-3702) struts2-cdi-plugin - memory never garbage colleted
Date Mon, 14 Nov 2011 17:27:51 GMT


Maurizio Cucchiara commented on WW-3702:

Hi guys,
I totally agree with Philip, furthermore I don't believe it fixes the problem. 
I have taken a deeper look at this issue last weekend. I also thought that the internal cache
could be a potential cause of memory leaks, but setting a breakpoint on the code I realized
that there were always 40 objects (not more) inside the cache. 
I ran the code example on Glassfish 3.1.1 and unfortunately I didn't experience the problem
that Marco mentioned before (I got the usual sawtooth wave). 
I also changed the code using the Spring Framework, but the outcome is more or less the same.
@Marco, I could be wrong but can you confirm the java vendor/version? 
Have you experienced this issue in other environments (it could be also a glassfish issue)?

> struts2-cdi-plugin - memory never garbage colleted
> --------------------------------------------------
>                 Key: WW-3702
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.2.1,, 2.2.3,
>         Environment: It happens regardless on Linux and Windows OS
> Proble encountered on both Glassfish 3.0.1 and Glassfish 3.1.1
> The JDK used is jdk1.6.0_24
>            Reporter: Marco Malavolta
>         Attachments: struts2-cdi-example.7z
> Every action execution that contains injected classes consume a small amout of memory
that after a while is stored in old-gen. This memory is never released after garbage collection.
> After a few days / week, depending on usage, my applications based on struts2 + struts2-cdi-plugin
are no more responsive.
> This forces me to restart the web server.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message