Tomcat JreMemoryLeakPreventionListener Testing scenario

2021-06-02 Thread S Abirami
Hi Team, As part of CISCAT Tomcat 9 benchmark, we have added JreMemoryLeakPreventionListener in server.xml. We understood that it prevents memory leak. Do you any tool (or) testcase to test this functionality is working fine in our product? Please let us know, if any input available.

Strange error with JSP

2021-06-02 Thread Christopher Schultz
All, I don't do too much work with JSPs, but I do have a few quick-and-dirty administrative things including one called the "session snooper" which just dumps out loads of information about the current user's session object. I'm getting this error in production, and I can reproduce it every

Re: Tomcat JreMemoryLeakPreventionListener Testing scenario

2021-06-02 Thread Christopher Schultz
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

Re: Strange error with JSP

2021-06-02 Thread Tim Funk
My guess? ClassNotFoundException is rooted in some other exception. Such as a different error is thrown during class initiation. Such as a static { doStuff();} block where doStuff does bad stuff. Hopefully there is more stack trace out there. If the JSP has static initializers - wrap them in try

Re: Strange error with JSP

2021-06-02 Thread Christopher Schultz
Tim, On 6/2/21 14:53, Tim Funk wrote: My guess? ClassNotFoundException is rooted in some other exception. Such as a different error is thrown during class initiation. Such as a static { doStuff();} block where doStuff does bad stuff. Hopefully there is more stack trace out there. If the JSP

Re: Strange error with JSP

2021-06-02 Thread Christopher Schultz
All, On 6/2/21 13:52, Christopher Schultz wrote: All, I don't do too much work with JSPs, but I do have a few quick-and-dirty administrative things including one called the "session snooper" which just dumps out loads of information about the current user's session object. I'm getting