В чем разница между «JVM thread_state» и «java.lang.Thread.State» в дампе потока? ⇐ JAVA

[Anonymous]

В приведенном ниже дампе потока показаны два разных состояния потока: JVM thread_state и java.lang.Thread.State. Каково фактическое состояние потока?
JVM thread_state имеет значение «_thread_blocked», а java.lang.Thread.State — «TIMED_WAITING»:
“Test” #867 daemon prio = 5 os_prio = 0 tid = 0x820009600000 nid =
0x1260e7 [JVM thread_state = _thread_blocked,
locked by VM(w / poll advisory bit)
waiting on VM lock 'self_suspend_monitor for TID 1204455',
polling bits:safep] java.lang.Thread
.State : TIMED_WAITING(parking)
at sun.misc.Unsafe.park(Native Method) -
locked(
a org.jctools.queues.MpscBlockingConsumerArrayQueue)
at java.util.concurrent.locks.LockSupport
.parkNanos(LockSupport.java : 215)
at org.jctools.queues.MpscBlockingConsumerArrayQueue
.parkUntilNext(MpscBlockingConsumerArrayQueue.java : 536)
at org.jctools.queues.MpscBlockingConsumerArrayQueue
.poll(MpscBlockingConsumerArrayQueue.java : 512)
at datadog.trace.agent.common.writer
.TraceProcessingWorker$TraceSerializingHandler
.consumeFromPrimaryQueue(TraceProcessingWorker.java : 254)
at datadog.trace.agent.common.writer
.TraceProcessingWorker$DaemonTraceSerializingHandler
.runDutyCycle(TraceProcessingWorker.java : 155)
at datadog.trace.agent.common.writer
.TraceProcessingWorker$DaemonTraceSerializingHandler
.run(TraceProcessingWorker.java : 145)
at java.lang.Thread.run(Thread.java : 807)


Подробнее здесь: https://stackoverflow.com/questions/791 ... ad-state-i