You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Marco Malavolta (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/11/11 09:52:52 UTC

[jira] [Issue Comment Edited] (WW-3702) struts2-cdi-plugin - memory never garbage colleted

    [ https://issues.apache.org/jira/browse/WW-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148351#comment-13148351 ] 

Marco Malavolta edited comment on WW-3702 at 11/11/11 8:52 AM:
---------------------------------------------------------------

Attached the struts2-cdi-example project, modified to reproduce the issue.

The archive contains also a readme.txt and some screenshots demostrating the problem
                
      was (Author: marco.malavolta):
    the struts2-cdi-example modified to reproduce the issue.

Contains also a readme.txt and some screenshots demostrating the problem
                  
> 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
>            Priority: Blocker
>         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