Gobs of DelegatingClassLoader Objects in JBoss Profiler

[evanschnell]

JDK: 1.5.0_04
JBoss 4.0.3 GA w/ Tomcat
Hibernate 3.0.5
One ear containing two wars.

No Hot Redeployments

My application does not do any hot deployments but I am seeing the behavior often associated with classloaders not being garbage collected on hot deploy. (http://forum.java.sun.com/thread.jspa?threadID=492509&messageID=2317057 )

Any HttpRequest, even the very first one after server startup, will consistently create at least 3 uncollectable DelegatingClassLoaders. A single user was able to create 113 of these chewing up 49K of RAM in just a couple of minutes. Are others seeing this? I found it while looking into a massive memory leak that exists at some customers but not others.

I investigated the relationship between the ClassNotFound issue fixed in 4.0.4 (http://jira.jboss.com/jira/browse/JBAS-3041)and the behavior I am seeing. I breakpointed ClassNotFoundException's constructors but this proved not useful due to extensive creation of these by BootstrapClassLoader. Does anyone know if this bug above only occurs when the class is not found by any ClassLoader or if it can occur for any ClassNotFoundException? I am unable to locate a case where my code silently catches ClassNotFoundException and I am not using a an MVC framework.

Any guidance would be much appreciated.

Evan[/url]

[genman]

You should be able to add logging (and a stack trace) to the constructor of this object to find out where these objects are getting created. If it's occuring during runtime, you should be able to track this issue down by turning off logging, starting the server, then turning on logging.

[genman]

You can also create Java exception breakpoints in Eclipse.