tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 56472] All classes remain in memory after stop of web application, when LDAP was used.
Date Fri, 02 May 2014 09:41:46 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=56472

--- Comment #6 from Stefan Frings <stefan_frings@qvc.com> ---
Created attachment 31585
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=31585&action=edit
New heap analysis after lib upgrade

I upgraded the cssparser.jar library from version 0.9.5 to 0.9.13. Now the
picture has changed a lot again.

The WebAppClassloader of my application has not path to GC Root anymore and is
now hold by a soft or weak reference.

But that did not finally solve my problem. All classes of my web application
still remain in memory even when I force a garbage collection several times. I
am still not able to restart the application (except by doubling the
PermGenSpace size).

My previous method to analyze the problem cause is not applicable anymore.
There is no class anymore that holds a strong reference to the
WebAppClassloader. What else can be the problem cause?

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message