运行方法内部的java线程状态冲突；为什么线程状态不是“正在运行”

我正在做一些测试，以了解java中不同的线程状态，并被一些查询所打动。
通常，当线程被示例化时，它被称为 "NEW" 状态，然后在调用 start （）方法，操作系统调度程序获得控制并处于 "RUNNABLE" 陈述并进一步说明 run() 由内部调用 start() 据说它处于运行状态。

Thread.currentThread().getState() // Returns the state of the thread

但是在执行下面的代码时观察到，线程状态永远不会显示为 "RUNNING" 即使在室内测试 run 方法。
有人能帮我理解为什么它会这样吗？

public static void main(String[] args) {
        System.out.println("Hello World");
        Thread t=new Thread(()->{
            System.out.println("Hi");
            System.out.println(Thread.currentThread().getState());  //// STATE DISPLAYED AS "RUNNABLE" AGAIN
        });
        System.out.println(t.getState());  // STATE DISPLAYED AS "NEW"
        t.start();
        System.out.println(t.getState());  // STATE DISPLAYED AS "RUNNABLE"
}

lambda表达式用于实现 run() 方法测试线程的状态，该状态再次显示为“runnable”而不是“running”

因为国家 RUNNING 不存在。如果你看看 getState 方法可以看到以下内容：

public State getState() {
    // get current thread state
    return jdk.internal.misc.VM.toThreadState(threadStatus);
}

如果你分析什么 State 是，您可以看到它是以下枚举：

public enum State {
        /**
         * Thread state for a thread which has not yet started.
         */
        NEW,

        /**
         * Thread state for a runnable thread.  A thread in the runnable
         * state is executing in the Java virtual machine but it may
         * be waiting for other resources from the operating system
         * such as processor.
         */
        RUNNABLE,

        /**
         * Thread state for a thread blocked waiting for a monitor lock.
         * A thread in the blocked state is waiting for a monitor lock
         * to enter a synchronized block/method or
         * reenter a synchronized block/method after calling
         * {@link Object#wait() Object.wait}.
         */
        BLOCKED,

        /**
         * Thread state for a waiting thread.
         * A thread is in the waiting state due to calling one of the
         * following methods:
         * <ul>
         *   <li>{@link Object#wait() Object.wait} with no timeout</li>
         *   <li>{@link #join() Thread.join} with no timeout</li>
         *   <li>{@link LockSupport#park() LockSupport.park}</li>
         * </ul>
         *
         * <p>A thread in the waiting state is waiting for another thread to
         * perform a particular action.
         *
         * For example, a thread that has called {@code Object.wait()}
         * on an object is waiting for another thread to call
         * {@code Object.notify()} or {@code Object.notifyAll()} on
         * that object. A thread that has called {@code Thread.join()}
         * is waiting for a specified thread to terminate.
         */
        WAITING,

        /**
         * Thread state for a waiting thread with a specified waiting time.
         * A thread is in the timed waiting state due to calling one of
         * the following methods with a specified positive waiting time:
         * <ul>
         *   <li>{@link #sleep Thread.sleep}</li>
         *   <li>{@link Object#wait(long) Object.wait} with timeout</li>
         *   <li>{@link #join(long) Thread.join} with timeout</li>
         *   <li>{@link LockSupport#parkNanos LockSupport.parkNanos}</li>
         *   <li>{@link LockSupport#parkUntil LockSupport.parkUntil}</li>
         * </ul>
         */
        TIMED_WAITING,

        /**
         * Thread state for a terminated thread.
         * The thread has completed execution.
         */
        TERMINATED;
    }

或从api thread.state：
public static enum thread.state扩展enum<thread.state>线程状态。线程可以处于以下状态之一：
尚未启动的新线程处于此状态。
在java虚拟机中执行的线程处于此状态。
阻塞等待监视器锁定而被阻塞的线程处于此状态。
正在无限期等待另一个线程执行特定操作的线程处于此状态。
timed\u waiting正在等待另一个线程执行某个操作达指定等待时间的线程处于此状态。
终止已退出的线程处于此状态。线程在给定的时间点只能处于一种状态。这些状态是不反映任何操作系统线程状态的虚拟机状态。

运行方法内部的java线程状态冲突；为什么线程状态不是“正在运行”

1条答案

相关问题

热门标签

最新问答