In window environment, tomcat8.5,cpu occupies 100%

CPU occupancy is as high as 60-70% for a period of time after tomcat is enabled.
Baidu, many people said to check in JavaStack, the following is a few thread information with high occupancy in jstack

"ajp-nio-8009-ClientPoller-1" -sharp55 daemon prio=5 os_prio=0 tid=0x000000001e51d000 nid=0x93e4 runnable [0x0000000028ade000]
   java.lang.Thread.State: 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$400(WindowsSelectorImpl.java:278)
    at sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
    at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
    - locked <0x00000000934c46b0> (a sun.nio.ch.Util$2)
    - locked <0x00000000934c46a0> (a java.util.Collections$UnmodifiableSet)
    - locked <0x00000000934c4530> (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:710)
    at java.lang.Thread.run(Thread.java:745)

   Locked ownable synchronizers:
    - None
"NioBlockingSelector.BlockPoller-2" -sharp16 daemon prio=5 os_prio=0 tid=0x000000001bdbe000 nid=0xa124 runnable [0x000000001d8df000]
   java.lang.Thread.State: 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$400(WindowsSelectorImpl.java:278)
    at sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
    at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
    - locked <0x000000009192fb18> (a sun.nio.ch.Util$2)
    - locked <0x000000009192fb08> (a java.util.Collections$UnmodifiableSet)
    - locked <0x000000009192f9a8> (a sun.nio.ch.WindowsSelectorImpl)
    at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
    at org.apache.tomcat.util.net.NioBlockingSelector$BlockPoller.run(NioBlockingSelector.java:298)

   Locked ownable synchronizers:
    - None
 at jar
Mar.31,2021

not encountered, provide a few inspection points. Take a look at the java version and print the thread stack a few more times to confirm that you just accidentally entered this method or almost always in this method. Restart it a few times to make sure that these threads consume CPU.

each time.

from the thread you give, it may be that the select method consumes more CPU,. You can find out whether the bug.
of jdk or tomcat, such as a serious BUG, of java nio leads to the problem of cpu or JAVA NIO

.

has been resolved, although the problem is unknown. I have checked that there is no problem with the thread before, and for the same project, I have CPU100%, here, but it is normal on the side of my colleagues. Doubt is the problem of the system itself, but due to the busy business, has been afraid to reinstall, until a few days ago to replace the new system, the problem solved.
original system: Lenovo-windows10 Family Chinese version
New system: Lenovo-windows10 Educational Edition

Menu