Use process explorer tracking to the CPU thread, as follows:
"HTTP - nio - 7004 - ClientPoller" daemon prio=5 # 37 os_prio=0 tid=0 x000000001c89b000 nid=0 x298c runnable x0000000020c4e000 [0]
Java. Lang. Thread. The State: a RUNNABLE
At sun. Nio. Ch. WindowsSelectorImpl $SubSelector. Poll0 (Native Method)
At sun. Nio. Ch. WindowsSelectorImpl $SubSelector. Poll (WindowsSelectorImpl. Java: 296)
At sun. Nio. Ch. WindowsSelectorImpl $SubSelector. Access the $400 (278) WindowsSelectorImpl. Java:
At sun. Nio. Ch. WindowsSelectorImpl. DoSelect (WindowsSelectorImpl. Java: 159)
At sun. Nio. Ch. SelectorImpl. LockAndDoSelect (SelectorImpl. Java: 86)
- locked & lt; 0 x00000000e127f8f8 & gt; (a sun. Nio. Ch. Util $3)
- locked & lt; 0 x00000000e127f8e8 & gt; (a Java. Util. Collections $UnmodifiableSet)
- locked & lt; 0 x00000000e127f668 & gt; (a sun. Nio. Ch. WindowsSelectorImpl)
At sun. Nio. Ch. SelectorImpl. Select (SelectorImpl. Java: 97)
At org.apache.tomcat.util.net.NioEndpoint$Poller.run NioEndpoint. Java: (709)
The at Java. Lang. Thread. The run (Thread. Java: 748)

Locked ownable synchronizers:
- None

CodePudding user response:

Most use jvisualvm monitoring, check the CPU thread is what