Could you please attempt to reproduce with the latest Jboss 3.2 branch and let us know what you find?
I do catch all throwables at this time, because I am insanely curious why the session threads have been disappearing for my application. It is usually not a good idea to catch Errors and the like, however for the time being I'm trying to get to the bottom of this. If you can 1) tell how to reproduce the problem 2) create a unit test case which reproduces the problem 3) supply a (better) fix and send it to either Adrian or even myself, we would be inclined to apply it to the tree. Personally, I think if Doug Lea says the threading model we have is problematic, then it probably is. In Java 1.5, the ThreadPoolExecutor is not going to allow for blocking enqueueing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822392#3822392 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822392 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
