https://bz.apache.org/bugzilla/show_bug.cgi?id=60578
Bug ID: 60578
Summary: Server CPU maxed out (100% per core) randomly after a
few hours
Product: Tomcat 8
Version: 8.0.14
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Connectors
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ----
On Debian stable since a few days the tomcat all of a sudden goes to next to
100% CPU.
Not much traffic is seen on the firewall .
Is this related to Bug 57544 ?
For the amount of cpu used, tomcat is astonishingly responsive.
Some have speculated that this is a subtle kind of DOS attack and with a
kill -QUIT
I get dozens of the two threads I don't before the cpu went high:
"http-nio-171.24.2.105-8443-exec-14" #13579 daemon prio=5 os_prio=0
tid=0x00007fa68c040000 nid=0x2352 runnable [0x00007fa614461000]
java.lang.Thread.State: RUNNABLE
at
org.apache.coyote.http11.AbstractInputBuffer.nextRequest(AbstractInputBuffer.java:244)
at
org.apache.coyote.http11.AbstractNioInputBuffer.nextRequest(AbstractNioInputBuffer.java:151)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1152)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:658)
at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:222)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1566)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1523)
- locked <0x0000000095c30eb8> (a
org.apache.tomcat.util.net.SecureNioChannel)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
"http-nio-171.24.2.105-ClientPoller-1" #112 daemon prio=5 os_prio=0
tid=0x00007fa6b4e84000 nid=0x45db runnable [0x00007fa61aff8000]
java.lang.Thread.State: RUNNABLE
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 <0x00000000866957c0> (a sun.nio.ch.Util$3)
- locked <0x00000000866957b0> (a java.util.Collections$UnmodifiableSet)
- locked <0x0000000086695688> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at
org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:1050)
at java.lang.Thread.run(Thread.java:745)
The same version of tomcat was in use without the phenomenon for weeks
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
