[
https://issues.apache.org/jira/browse/WW-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202579#comment-13202579
]
Maurizio Cucchiara commented on WW-3751:
----------------------------------------
Ciao Marco,
I have just tried the example you provided and I can confirm the presence of
the issue on Glassfish (apropos, thank you for the accurate and clear test
case).
At the same time, I have to say you that the error does not occur under Tomcat
neither under Jetty (which would make me think that this is a Glassfish issue).
Under both the application servers, the tenured gen memory has never exceeded
20MB in size (though Jetty is much slower than Tomcat).
I'm trying to understand what really differs from Glassfish and I'll ping you
back.
> Memory leak using jsp tags on an app deployed on glassfish
> ----------------------------------------------------------
>
> Key: WW-3751
> URL: https://issues.apache.org/jira/browse/WW-3751
> Project: Struts 2
> Issue Type: Bug
> Components: Other
> Affects Versions: 2.2.1, 2.2.1.1, 2.2.3, 2.3.1, 2.3.1.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 Linux
> Reporter: Marco Malavolta
> Attachments: screenshot-1 - VisualVM.jpg, testproject.zip
>
>
> 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 irresponsiveness.
> I also created a Jira issue on GlassFish
> (http://java.net/jira/browse/GLASSFISH-18316), 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
