问题场景:公司有几个项目总是在运行一段时间后,总是出于卡死状态,接口请求后无任何响应,然后排查日志和服务器性能指标,发现没有出现内存泄露和内存溢出,服务器剩余空间也足够大。说明可能存在其他问题。
问题排查 jstack -l 出现问题的java进程号
查看服务器的线程运行情况
出现了以下报错信息
"WebSocketServer-/live-1304" prio=10 tid=0x00007f055c001000 nid=0xeea5 waiting on condition [0x00007f04f1d7b000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000004eb2424b8> (a java.util.concurrent.SynchronousQueue$TransferStack)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
"DubboClientHandler-10.9.152.203:18889-thread-382" daemon prio=10 tid=0x00007f05640e4000 nid=0xeb30 waiting on condition [0x00007f04f1e3e000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000004ecbe6d28> (a java.util.concurrent.SynchronousQueue$TransferStack)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
出现线程等待超时报错,说明什么问题?说明线程池现在释放的无法满足等待的队列,导致等待的超时异常,然后再向dba要生产环境的tomcat线程池配置信息
<Connector port="8214" protocol="org.apache.coyote.http11.Http11NioProtocol"
URIEncoding="UTF-8"
maxThreads="800" maxConnections="800" acceptCount="800"
enableLookups="false" redirectPort="8443"
maxKeepAliveRequests="1"
compression="on"
noCompressionUserAgents="gozilla,traviata" />
然后添加
minSpareThreads=“100”
maxSpareThreads=“500”
maxSpareThreads当线程使用超过500时,会主动强制回收一些线程来用于满足新的线程需要,然后上线后,果断解决问题,没有再出现线程池数量不够,线程等待的问题出现。