Since we upgraded the concurrent.jar, we have not seen this problem re-occur. I see no harm in trying it out. From the size of the jar distributed with 4.0.1, I suspect it is not the latest version.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866998#3866998 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866998 ------------------------------------------------------- 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