struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukasz Lenart (JIRA)" <>
Subject [jira] [Updated] (WW-3751) Memory leak using jsp tags on an app deployed on glassfish
Date Sun, 28 Oct 2012 21:51:13 GMT


Lukasz Lenart updated WW-3751:

    Fix Version/s: 2.3.7
> Memory leak using jsp tags on an app deployed on glassfish
> ----------------------------------------------------------
>                 Key: WW-3751
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.2.1,, 2.2.3, 2.3.1,
>         Environment: Windows 7 Professional (Microsoft Windows version 6.1 Build 7601:Service
Pack 1) 64 bit
> Processor: Intel Core i5 CPU 650 @ 3.20GHz 3.33 Ghz
> Ram: 6.00 GB
> GlassFish Server Open Source Edition 3.1.1 (build 12).
> It also happens in production environment with different hardware configuration running
>            Reporter: Marco Malavolta
>             Fix For: 2.3.7
>         Attachments: screenshot-1 - VisualVM.jpg,
> I have some webapps based on Struts 2 framework.
> I use JSP tags, even sometimes with nested Struts 2 tag (FreeMarker).
> Every time you call with a single jsp jsp tags JspWriterImp a new instance is created
with more or less the contents of the tag (instead of reusing the same object stored in memory.
> This causes a loss of memory, because these objects are located in the old generation
heap 'til the web application is restarted
> After a few days / weeks depending on the traffic that you need to restart because of
> I also created a Jira issue on GlassFish (,
where I posted a screenshot and a sample application to reproduce the problem.
> Basically I'm not sure if it's a struts problem or a problem of glass fish.
> Perhaps the second hypothesis is more likely
> Feel free to close it if you feel that the problem is solely related to Glassfish

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

View raw message