Upon further testing, 4.0.2RC1 is far worse that its predecessors about leaking its jars to the applications encapsulated in EARs.
The latest leak problem I discovered is now with commons-collections. Logging-related leaks were bad, but commons-collections is used so widely that it has thorougly disabled all of our database access. The latest exception is "java.lang.NoClassDefFoundError: org/apache/commons/collections/SequencedHashMap", and it does not occur on ANY of the previous versions. Seems like the same cause, different symptom. Can't class leakage from jBoss/Tomcat to the EARs be prevented once and for all? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870429#3870429 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870429 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
