It was the only way I found to implement a timeout behavior that had a chance of working when there were uncooperative tasks. See the org.jboss.test.util.test. ThreadPoolTaskUnitTestCase.testCompleteTimeoutWithSpinLoop as an example.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Brock Sent: Saturday, February 04, 2006 2:33 PM To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] BasicThreadPool and Thread.stop() I don't think it is a good idea to invoke Thread.stop(). This has memory leak problems. Why was this introduced? The pooled threads are already daemon threads so they should not stop the system from exiting at shutdown. If you are not shutting down the system, then any objects on the stopped thread's stack are not garbage collected. -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
