On May 22, 10:19 am, Kirk <kirk.pepperd...@gmail.com> wrote: > For example, if you have a application class implementing an interface from > the bootstrap classloader, it is possible that this relationship, which is > expressed in the object reference chains, will keep your classes metadata > live. Because your class is live, the classloader that loaded it will be > live. Since the classloader is live, *all* of the classes referenced by that > classloader will be kept live. Which means in the context of an application > server, that products logic may "unload" an application and reload the new > version but that intricate little reference chain from the bootstrap > classloader (or the extension or the application or another tiered loader) > will prevent everything from being GC'ed.
Wouldn't that mean that class loaders are effectively never collected, which doesn't appear to be true. There are ClassLoader leaks associated with the Java libraries, including ThreadLocal, JDBC DriverManager and Java Beans. Tom Hawtin -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
