Sorry, forgot to mention: tomcat 4.1.18, jdk 1.4.1_01 on linux.
Joseph Shraibman wrote:
One of my classes creates a static ThreadGroup. I notice that when I
update a class and tomcat reloads that context the ThreadGroup is still
around. If the ThreadGroup is still around that means the old class is
still around, which means that class loader is still around. Why is it
still around? I tried making the ThreadGroup daemon but it didn't help.
I think the fact that the old class loaders are still around goes a long
way to explaining why tomcat takes up so much memory.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>