Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Message-ID: <BAY406-EAS244C4435790B803714DF87396E00@phx.gbl>
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
From: Chen Levy <chen_levy@hotmail.com>
Subject: High CPU Consumption with Tomcat 8.5.4 NIO and SSL
Date: Tue, 30 Aug 2016 09:11:14 -0400
Importance: normal
Content-Type: multipart/alternative;
	boundary="_2564E8BE-6EBF-413C-8A9E-5C878F288606_"
archived-at: Tue, 30 Aug 2016 13:12:28 -0000

--_2564E8BE-6EBF-413C-8A9E-5C878F288606_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hello All

Since Tomcat 8.0.x development is about to be stopped, we=E2=80=99ve decide=
d to switch to 8.5.4, but since are facing the following issue:
A few hours after startup, the Java process starts consuming 100% CPU, and =
while Tomcat is still responsive, it is very slow. This is consistent, been=
 going on for a couple of weeks and is only resolved each time by restartin=
g Tomcat.

I=E2=80=99ve tried a few things:
Reverted back to Tomcat 8.0.33 -> problem solved
Switched from NIO to NIO2 -> problem solved, but other issues appeared with=
 connections ending prematurely, so not a valid option
Switched to the new connector configuration scheme -> problem persists

Setup:=20
Current Amazon Linux, Tomcat 8.5.4, Java 1.8.0_92-b14, no APR

      <Connector port=3D"443" protocol=3D"org.apache.coyote.http11.Http11Ni=
oProtocol"
                   maxThreads=3D"500" minSpareThreads=3D"25"
                   enableLookups=3D"false" disableUploadTimeout=3D"true"
                   connectionTimeout=3D"10000"
                   compression=3D"on"
                   compressionMinSize=3D"2048"
                   compressableMimeType=3D"text/html,text/xml,text/json,tex=
t/javascript,text/css,text/plain,application/javascript,application/x-javas=
cript,application/xml"
                   SSLEnabled=3D"true" scheme=3D"https" secure=3D"true">
            <SSLHostConfig protocols=3D"TLSv1,TLSv1.1,TLSv1.2">
                <Certificate certificateKeystoreFile=3D"conf/tomcat.keystor=
e"
                             certificateKeyAlias=3D"tomcat"
                             certificateKeystorePassword=3D"tomcat"
                             certificateKeystoreType=3D"PKCS12"/>
            </SSLHostConfig>
        </Connector>


Analyzing the threads, there=E2=80=99s one which takes all of the CPU time:

"https-jsse-nio-8443-ClientPoller-0" daemon prio=3D5 RUNNABLE
	sun.misc.Unsafe.unpark(Native Method)
	java.util.concurrent.locks.LockSupport.unpark(LockSupport.java:141)
	java.util.concurrent.locks.AbstractQueuedSynchronizer.unparkSuccessor(Abst=
ractQueuedSynchronizer.java:662)
	java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueu=
edSynchronizer.java:1264)
	java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457)
	java.util.concurrent.LinkedBlockingQueue.signalNotEmpty(LinkedBlockingQueu=
e.java:176)
	java.util.concurrent.LinkedBlockingQueue.offer(LinkedBlockingQueue.java:43=
0)
	org.apache.tomcat.util.threads.TaskQueue.offer(TaskQueue.java:74)
	org.apache.tomcat.util.threads.TaskQueue.offer(TaskQueue.java:31)
	java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:13=
61)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.execute(ThreadPoolExecut=
or.java:163)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.execute(ThreadPoolExecut=
or.java:141)
	org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint=
.java:828)
	org.apache.tomcat.util.net.NioEndpoint$Poller.processKey(NioEndpoint.java:=
850)
	org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:826)
	java.lang.Thread.run(Thread.java:745)


This is similar to an issue on a Windows machine reported here:
http://marc.info/?l=3Dtomcat-user&m=3D147082413626214&w=3D2

I=E2=80=99ll appreciate any insight or advice
Thanks in advance
Chen


--_2564E8BE-6EBF-413C-8A9E-5C878F288606_--