https://bz.apache.org/bugzilla/show_bug.cgi?id=64771
Bug ID: 64771
Summary: Windows CPU processor getting locked by a thread
reading request body from https connection
Product: Tomcat 9
Version: 9.0.37
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: Util
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: -----
Created attachment 37472
--> https://bz.apache.org/bugzilla/attachment.cgi?id=37472&action=edit
Java Thread Dump
The problem started with windows CPU always keep at 25%, but it should be
around 2-7% is there is no request.
I use windows ProcessExplorer identified that one thread is reading request
body from an https connection but there is no request at that time based on the
audit logs, and the thread has been running more than 2 hours.
I use windows ProcessExplorer and jdk jstack identified the thread "0xd14" is
always keep running even there is no request to Tomcat.
"boundedElastic-90" #434 daemon prio=5 os_prio=0 tid=0x0000000021055000
nid=0xd14 runnable [0x000000004383d000]
java.lang.Thread.State: RUNNABLE
at
org.apache.tomcat.util.net.openssl.OpenSSLEngine.unwrap(OpenSSLEngine.java:603)
- locked <0x0000000608ad2bf0> (a
org.apache.tomcat.util.net.openssl.OpenSSLEngine)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
"I/O dispatcher 3" #30 prio=5 os_prio=0 tid=0x00000000208d2800 nid=0x17e8
waiting for monitor entry [0x0000000024ace000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.tomcat.util.net.openssl.OpenSSLEngine.wrap(OpenSSLEngine.java:391)
- waiting to lock <0x0000000608ad2bf0> (a
org.apache.tomcat.util.net.openssl.OpenSSLEngine)
at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469)
at
org.apache.tomcat.util.net.SecureNioChannel.write(SecureNioChannel.java:802)
I try to understand the source "OpenSSLEngine" based on the thread logs, it
seems that the reading request body is not yet fully completed but the request
connection is closed by the caller.
I need help to have a fix to prevent this kind of problem happen in Tomcat to
prevent such problem happen in production.
--
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]
