tomcat cpu占用过高的问题

[妈了个鸡腿]

确定是以下两个Thread占用过高，求问如何解决？

"ajp-nio-8009-ClientPoller-0" #53 daemon prio=5 os_prio=0 tid=0x000000001af75800 nid=0x3f6c runnable [0x000000001f38e000]
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 <0x000000008045c548> (a sun.nio.ch.Util$3)
- locked <0x000000008045c538> (a java.util.Collections$UnmodifiableSet)
- locked <0x000000008045c3c8> (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:825)
at java.lang.Thread.run(Thread.java:748)

Locked ownable synchronizers:
- None


"NioBlockingSelector.BlockPoller-2" #25 daemon prio=5 os_prio=0 tid=0x000000001a6a6000 nid=0x2c2c runnable [0x000000001c7bf000]
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 <0x0000000080473840> (a sun.nio.ch.Util$3)
- locked <0x0000000080473830> (a java.util.Collections$UnmodifiableSet)
- locked <0x0000000080469600> (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

[妈了个鸡腿]

引用 1 楼 Abel_Shen_G 的回复:

windows下可以试试性能查看

可以说具体点么？

[Blue_Shen_SH]

windows下可以试试性能查看

[「已注销」]

优化下代码

[K G]

你是不是设置成主线程了

[妈了个鸡腿]

回复一下，我是在虚拟机里调试的时候重新部署就很容易出现cpu很高的问题，但是在使用时暂时还没有出现这种情况。