vincent2518 opened a new issue #6797:
URL: https://github.com/apache/skywalking/issues/6797


   Why does the client have so many (64) resident threads in Runnable state?
   
   thread dumps are like below:
   at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)           at 
sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)           at 
sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)           at 
sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)           - 
locked [0x00000006c0c4cf40] (a            
org.apache.skywalking.apm.dependencies.io.netty.channel.nio.SelectedSelectionKeySet)
           - locked [0x00000006c0c4d030] (a            
java.util.Collections$UnmodifiableSet)           - locked [0x00000006c0c4cf58] 
(a sun.nio.ch.EPollSelectorImpl)           at 
sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)           at            
org.apache.skywalking.apm.dependencies.io.netty.channel.nio.SelectedSelectionKeySetSelector.select(SelectedSelectionKeySetSelector.java:62)
           at            
org.apache.skywalking.apm.dependencies.io.netty.channel.nio.NioEventLoop.select(NioEventLoop.java:824)
           at            org.apache.skywalking.ap
 m.dependencies.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:457)    
       at            
org.apache.skywalking.apm.dependencies.io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1044)
           at            
org.apache.skywalking.apm.dependencies.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
           at            
org.apache.skywalking.apm.dependencies.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
           at java.lang.Thread.run(Thread.java:745)
   --
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to