What is the version of your tomcat? 5.5 supposed to have resolved this issue
by flush reflection cache when undeploy your web app.
-Original Message-
From: Andy Kriger [mailto:[EMAIL PROTECTED]
Sent: June 27, 2005 12:12 PM
To: tomcat-user@jakarta.apache.org
Subject: Please help with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phillip Qin wrote:
What is the version of your tomcat? 5.5 supposed to have resolved this issue
by flush reflection cache when undeploy your web app.
I get this with 5.5.9, using jdk 1.5, under Solaris 8, when I copy my
new beehive-based webapp
method. Otherwise, you will have to go through your web app carefully to
find out if there is any memory leak.
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]
Sent: June 27, 2005 1:25 PM
To: Tomcat Users List
Subject: Re: Please help with PermGen OutOfMemory error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phillip Qin wrote:
I did see this issue happened with my tomcat 4.1/5.0. After I upgraded to
5.5, I have encountered any outofmemory even after 100 hundreds deployments.
Does your web app use struts? You can always clean up resource by adding
As per tools - I think you can use JMeter. It gives u some pretty
useful graphs and analysis.
-Anoop
On 6/27/05, James Black [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phillip Qin wrote:
I did see this issue happened with my tomcat 4.1/5.0. After I upgraded to
