> 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.
In any event, calling this problem a "myth" is just plain wrong. It *is* a real problem, regardless if it's a an intentional design decision or not that only in recent years started to manifest itself. For all practical purposes, garbage collection may effectively be considered broken by anyone not intimately familiar with the JVM memory model. -- 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.
