[
https://issues.apache.org/jira/browse/WW-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150332#comment-13150332
]
Marco Malavolta commented on WW-3702:
-------------------------------------
Hi to all.
@Maurizio, I can confirm the java version. I also tried to lower the max memory
to 256MB from 512MB for glassfish (with 128MB the old gen was nearly full after
starting the server and deploying the application) and the application slows
'til unresponsiveness in about half the time (about 156000 requests in 46
minutes), so the beahviour seems predictable.
I've never tested the application in environments other than glasshfish, cause
in my applications I use dependency injection and ejb support.
I think I will take a look at TomEE in a few days. If the problem doesn't
affect it, I'll try to promote the switch in production.
Just to know, does any of you has experienced the same problem and can confirm
it?
> struts2-cdi-plugin - memory never garbage colleted
> --------------------------------------------------
>
> Key: WW-3702
> URL: https://issues.apache.org/jira/browse/WW-3702
> Project: Struts 2
> Issue Type: Bug
> Components: Other
> Affects Versions: 2.2.1, 2.2.1.1, 2.2.3, 2.2.3.1
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
