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. waiting to lock (a .)Īt .wrap(SSLEngine.java:469)Īt .(SecureNioChannel.java:802) : BLOCKED (on object monitor)Īt .(OpenSSLEngine.java:391) locked (a .)Īt .unwrap(SSLEngine.java:624) I use windows ProcessExplorer and jdk jstack identified the thread "0xd14" is always keep running even there is no request to Tomcat. 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.
The problem started with windows CPU always keep at 25%, but it should be around 2-7% is there is no request.
0 kommentar(er)
