On Mon, 2006-02-06 at 01:06, Jason T. Greene wrote:
Actually the behavior you describe is the semantics of Thread.destroy()
if it were actually implemented. Thread.stop() just forces the targeted
thread to throw a ThreadDeath exception. This causes all finally blocks
to execute, and in fact if
PROTECTED] [mailto:jboss-
[EMAIL PROTECTED] On Behalf Of Adrian Brock
Sent: Monday, February 06, 2006 3:25 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] BasicThreadPool and Thread.stop()
Thanks for the clarification. Re-reading this:
http://java.sun.com/j2se/1.5.0/docs
: RE: [JBoss-dev] BasicThreadPool and Thread.stop()
On Sat, 2006-02-04 at 17:44, Scott M Stark wrote:
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
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
:[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
be to automatically trigger a reboot if you
detect a misbehaving thread.
-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
: [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
] 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
