2016-03-10 22:54 GMT+03:00 Christopher Schultz <ch...@christopherschultz.net>: > Rallavagu, > > On 3/10/16 2:11 PM, Rallavagu wrote: >> From a thread dump and corresponding "top" output it is reported >> that the following thread is consuming significant CPU (around >> 80%) >> >> "http-bio-28080-exec-437" daemon prio=10 tid=0x00007f4acc0de000 >> nid=0x54ce waiting on condition [0x00007f4b038f7000] >> java.lang.Thread.State: TIMED_WAITING (parking) at >> sun.misc.Unsafe.park(Native Method) - parking to wait for >> <0x000000071846da50> (a >> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) >> >> > at >> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) >> >> > at >> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject. > awaitNanos(AbstractQueuedSynchronizer.java:2082) >> >> at >> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java > :467) >> >> > at org.apache.tomcat.util.threads.TaskQueue.poll(TaskQueue.java:86) >> at >> org.apache.tomcat.util.threads.TaskQueue.poll(TaskQueue.java:32) >> at >> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.jav > a:1068) >> >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j > ava:1130) >> >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. > java:615) >> >> at java.lang.Thread.run(Thread.java:744) >> >> Considering it is a thread from tomcat's thread pool and it >> suggests that it is "java.lang.Thread.State: TIMED_WAITING >> (parking)" wonder why this shows up as consuming high CPU. Any >> clues would be highly appreciated. Thanks in advance. > > Are you sure you have matched-up the correct thread within the JVM > that is using all that CPU? > > How are you measuring the CPU usage? > > Can you post your <Connector> and/or <Executor> configuration?
Also 1. Tomcat version =? 2. Java version =? 3. You need to take several (e.g. 3) thread dumps to see whether there is some progress /change of state. The last similar thread in search results for users@ list is in May 2015 "High cpu on Tomcat 8", a year ago. As there were no such threads recently, I think that bug has already been fixed. The only Tomcat code in that stacktrace is org.apache.tomcat.util.threads.TaskQueue. The connector type can be guessed as "bio" from the thread name, but as a thread name can be configured on an Executor, this identification is not reliable. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
