Caldarale, Charles R wrote:
From: Ognjen Blagojevic [mailto:ogn...@etf.bg.ac.rs]
Subject: Debugging PermGen problems
Environment: Tomcat 6.0.14, Windows XP SP2.
Before doing *anything* else, move up to the current level (6.0.26). Besides
having numerous stability and security fixes beyond
Hi,
My co-worker and I decided to try to debug PermGen problems after
detailed reading of mailing list archives and Tomcat wiki.
We followed the procedure described at the wiki [1], and got one
inactive WebappClassLoader (started = false), with 18 GC root paths.
They are attached to the
From: Ognjen Blagojevic [mailto:ogn...@etf.bg.ac.rs]
Subject: Debugging PermGen problems
Environment: Tomcat 6.0.14, Windows XP SP2.
Before doing *anything* else, move up to the current level (6.0.26). Besides
having numerous stability and security fixes beyond your nearly three-year old
Hi,
My co-worker and I decided to try to debug PermGen problems after
detailed reading of mailing list archives and Tomcat wiki.
We followed the procedure described at the wiki [1], and got one
inactive WebappClassLoader (started = false), with 18 GC root paths.
They are attached
From: Martin Gainty [mailto:mgai...@hotmail.com]
Subject: RE: Debugging PermGen problems
if the database is only being referenced by that webapp then put the
postgresql-*.jars into WEB-INF/lib
You can't do that if Tomcat is managing the DB connection pool - the driver jar
must be placed
