Abirami,
On 6/2/21 03:06, S Abirami wrote:
Hi Team,
As part of CISCAT Tomcat 9 benchmark, we have added
JreMemoryLeakPreventionListener in server.xml.
We understood that it prevents memory leak.
If you never reload your web application at runtime (i.e. if you always
bounce Tomcat entirely to reload your application), then the
JREMemoryLeakPreventionListener will accomplish nothing for you. It only
prevents cross-application-reload memory leaks.
Do you any tool (or) testcase to test this functionality is working fine in our
product?
Please let us know, if any input available.
Try to use Java AWT from your application and then see if it cleanly
unloads (including the ClassLoader being reclaimed by the GC).
Read the documentation for the Listener and, honestly, read the source
code of the class to see all the weird things Tomcat will trigger for
you to avoid pinning your application's ClassLoader in memory.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
