为什么废弃stop方法
终断一个线程，可以用thread.interrupt( ) 和stop方法。
stop现在已经废弃，不推荐使用。
stop 是不安全的，通过与interrupt()的比较，可以看到stop是哪里不安全。
代码如下：

public class ThreadTest {public static void main(String[] args) {try {System.out.println("try");Thread thread = new MyThread();thread.start();thread.stop();// thread.interrupt();} catch (Exception e) {System.out.println("exception");} finally {System.out.println("finally");}}}class MyThread extends Thread {public void run() {try {System.out.println("run");Thread.sleep(1000L);throw new Exception();} catch (Exception e) {System.out.println("exception ");}}}

console输出的结果是：
try
finally

可以看到，stop终结一个线程，并且释放监控线程的所有资源。对于主线程来说，并不能再跟踪线程的运行状况，当线程出现异常也不能被捕获。而其他线程并不知道被stop的线程出现了异常。这样导致状态不一致的情况产生。

注释掉stop 一行，换用interrupt,进行测试。输出结果是：
try
finally
run
exception



以下是jdk的英文。

 /**      * Forces the thread to stop executing.     * <p>     * If there is a security manager installed, its <code>checkAccess</code>     * method is called with <code>this</code>      * as its argument. This may result in a      * <code>SecurityException</code> being raised (in the current thread).      * <p>     * If this thread is different from the current thread (that is, the current     * thread is trying to stop a thread other than itself), the     * security manager's <code>checkPermission</code> method (with a     * <code>RuntimePermission("stopThread")</code> argument) is called in     * addition.     * Again, this may result in throwing a      * <code>SecurityException</code> (in the current thread).      * <p>     * The thread represented by this thread is forced to stop whatever      * it is doing abnormally and to throw a newly created      * <code>ThreadDeath</code> object as an exception.      * <p>     * It is permitted to stop a thread that has not yet been started.      * If the thread is eventually started, it immediately terminates.      * <p>     * An application should not normally try to catch      * <code>ThreadDeath</code> unless it must do some extraordinary      * cleanup operation (note that the throwing of      * <code>ThreadDeath</code> causes <code>finally</code> clauses of      * <code>try</code> statements to be executed before the thread      * officially dies).  If a <code>catch</code> clause catches a      * <code>ThreadDeath</code> object, it is important to rethrow the      * object so that the thread actually dies.      * <p>     * The top-level error handler that reacts to otherwise uncaught      * exceptions does not print out a message or otherwise notify the      * application if the uncaught exception is an instance of      * <code>ThreadDeath</code>.      *     * @exception  SecurityException  if the current thread cannot      *               modify this thread.     * @see        #interrupt()     * @see        #checkAccess()     * @see        #run()     * @see        #start()     * @see        ThreadDeath     * @see        ThreadGroup#uncaughtException(Thread,Throwable)     * @see        SecurityManager#checkAccess(Thread)     * @see        SecurityManager#checkPermission     * @deprecated This method is inherently unsafe.  Stopping a thread with     *     Thread.stop causes it to unlock all of the monitors that it     *     has locked (as a natural consequence of the unchecked     *     <code>ThreadDeath</code> exception propagating up the stack).  If     *       any of the objects previously protected by these monitors were in     *       an inconsistent state, the damaged objects become visible to     *       other threads, potentially resulting in arbitrary behavior.  Many     *       uses of <code>stop</code> should be replaced by code that simply     *       modifies some variable to indicate that the target thread should     *       stop running.  The target thread should check this variable       *       regularly, and return from its run method in an orderly fashion     *       if the variable indicates that it is to stop running.  If the     *       target thread waits for long periods (on a condition variable,     *       for example), the <code>interrupt</code> method should be used to     *       interrupt the wait.      *       For more information, see      *       <a href="{@docRoot}/../technotes/guides/concurrency/threadPrimitiveDeprecation.html">Why      *       are Thread.stop, Thread.suspend and Thread.resume Deprecated?</a>.     */    @Deprecated    public final void stop() {        // If the thread is already dead, return.// A zero status value corresponds to "NEW".if ((threadStatus != 0) && !isAlive()) {    return;}stop1(new ThreadDeath());    }