Just for completeness, JBoss already jumps through hoops to try to avoid the problem including scheduling classloading across threads and retrying the classloading if it hits the error.
But since the problem is non-deterministic (like all non-thread-safe bugs), any work around (except one that avoids concurrent usage) is not guaranteed to work. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886464#3886464 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886464 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
