This has been discussed quite a lot on mailing list. Lots of things can
generate memory leaks in webapp environment. Amongst others:
- not nullifying threadlocal variable.
- use of singleton pattern
- some bugged versions of CGlib
take a look at older messages in this mailing list
http://marc.thea
> Im a Project Manager, not a techie but we had the same problem and had to
> increase the perm gen to the following: Tomcat sets it at default at 64MB.
> Perm Gen Memory: 150 MB
> Max Perm Gen: 256 MB
Perm gen is memory reserved for class loading and is directly proportional to
the number/size
y, 15 September, 2006 09:59
| To: Tomcat Users List
| Subject: Perm Gen not being released in GC
|
| Hi All,
|
|
|
| Throughput Garbage collection on a 5.5.15 Tomcat instance is failing
to
| release Old Gen heap space when it becomes full on one of our Windows
| installations.
|
|
|
| For the most
ers List"
rnd.com> cc:
Subject: Re: Perm Gen not being
Darren,
Every now and then JConsole shows Old Gen as having flat-lined.
Only a Tomcat restart can rectify the problem. Killing sessions
followed by a manual GC does not seem to have an effect.
Haven't yet determined whether we need to start looking at the
young to old heap allocation ra
Hi All,
Throughput Garbage collection on a 5.5.15 Tomcat instance is failing to
release Old Gen heap space when it becomes full on one of our Windows
installations.
For the most part GC does release memory - in a typical working day this is
an upward trend in terms of the amount of heap rec