hibernate 100% CPU,使用Tomcat池

bpzcxfmw  于 2023-04-06  发布在  其他
关注(0)|答案(1)|浏览(158)

下面是线程导致100%的CPU使用率随机,它只解决当节点重新启动,需要帮助确定根本原因,我的猜测是有关的一些循环,导致CPU SPIKE

stackTrace:
java.lang.Thread.State: RUNNABLE\
at javax.net.ssl.SSLEngineResult.<init>(java.base@11.0.18/SSLEngineResult.java:196)\
at sun.security.ssl.SSLEngineImpl.writeRecord(java.base@11.0.18/SSLEngineImpl.java:164)\
at sun.security.ssl.SSLEngineImpl.wrap(java.base@11.0.18/SSLEngineImpl.java:136)\
- eliminated <0x00000000c5c5ebb8> (a sun.security.ssl.SSLEngineImpl)\
at sun.security.ssl.SSLEngineImpl.wrap(java.base@11.0.18/SSLEngineImpl.java:116)\
- locked <0x00000000c5c5ebb8> (a sun.security.ssl.SSLEngineImpl)\
at javax.net.ssl.SSLEngine.wrap(java.base@11.0.18/SSLEngine.java:482)\
at oracle.net.nt.SSLSocketChannel.shutdown(SSLSocketChannel.java:381)\
- locked <0x00000000c5c5e868> (a oracle.net.nt.SSLSocketChannel)\
at oracle.net.nt.SSLSocketChannel.write(SSLSocketChannel.java:242)\
at oracle.net.ns.NIOPacket.writeToSocketChannel(NIOPacket.java:302)\
at oracle.net.ns.NIONSDataChannel.writeDataToSocketChannel(NIONSDataChannel.java:173)\
at oracle.net.ns.NIONSDataChannel.writeDataToSocketChannel(NIONSDataChannel.java:124)\
at oracle.jdbc.driver.T4CMAREngineNIO.flush(T4CMAREngineNIO.java:727)\
at oracle.jdbc.driver.T4CMAREngineNIO.prepareForUnmarshall(T4CMAREngineNIO.java:733)\
at oracle.jdbc.driver.T4CMAREngineNIO.unmarshalUB1(T4CMAREngineNIO.java:413)\
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:485)\
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)\
at oracle.jdbc.driver.T4C7Ocommoncall.doOCOMMIT(T4C7Ocommoncall.java:72)\
at oracle.jdbc.driver.T4CConnection.doCommit(T4CConnection.java:961)\
- eliminated <0x00000000c5c59900> (a oracle.jdbc.driver.T4CConnection)\
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:1937)\
- locked <0x00000000c5c59900> (a oracle.jdbc.driver.T4CConnection)\
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:1942)\
at jdk.internal.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)\
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.18/DelegatingMethodAccessorImpl.java:43)\
at java.lang.reflect.Method.invoke(java.base@11.0.18/Method.java:566)\
at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:131)\
at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)\
at org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:79)\
at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)\
at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)\
at com.sun.proxy.$Proxy81.commit(Unknown Source)\
at org.hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.commit(AbstractLogicalConnectionImplementor.java:86)\
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:282)\
at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:101)\
at io.dropwizard.hibernate.SessionFactoryHealthCheck.lambda$check$0(SessionFactoryHealthCheck.java:56)\
at io.dropwizard.hibernate.SessionFactoryHealthCheck$$Lambda$797/0x0000000840b16440.call(Unknown Source)\
at java.util.concurrent.FutureTask.run(java.base@11.0.18/FutureTask.java:264)\
at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@11.0.18/ThreadPoolExecutor.java:1128)\
at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@11.0.18/ThreadPoolExecutor.java:628)\
at com.codahale.metrics.InstrumentedThreadFactory$InstrumentedRunnable.run(InstrumentedThreadFactory.java:66)\
at java.lang.Thread.run(java.base@11.0.18/Thread.java:834)\
Locked ownable synchronizers:\
- <0x00000000c2c9c570> (a java.util.concurrent.ThreadPoolExecutor$Worker)\
bkhjykvo

bkhjykvo1#

本周我们在ou服务器(java 17,spring Boot ,...)和SQL Server数据库上遇到了完全相同的问题。
通过禁用TLS 1.3解决了这个问题,但我们还需要进一步调查以找到根本原因(再次启用TLS 1.3会很好)。
似乎与此有关:https://jira.atlassian.com/browse/JRASERVER-70169

相关问题