2017-03-28 47 views
0

我使用tomcat服务器,当我拿到线程转储我可以看到许多线程被阻塞(172)和其他线程IN_NATIVE(27)。几乎很多堵塞的线程就像下面的smiler。有人能帮助什么可能是原因吗?我的8GB OldGen空间已满。执行GC后也不释放。许多线程被阻塞,并从老根存储器不释放

阻塞的线程:

Thread 22614 - threadId:Thread 22614 - state:BLOCKED 
stackTrace: 
- java.net.SocketInputStream.socketRead0(java.io.FileDescriptor, byte[], int, int, int) @bci=0 (Compiled frame; information may be imprecise) 
- java.net.SocketInputStream.read(byte[], int, int, int) @bci=87, line=152 (Compiled frame) 
- java.net.SocketInputStream.read(byte[], int, int) @bci=11, line=122 (Compiled frame) 
- org.apache.coyote.http11.InternalInputBuffer.fill(boolean) @bci=59, line=512 (Compiled frame) 
- org.apache.coyote.http11.InternalInputBuffer.fill() @bci=2, line=497 (Compiled frame) 
- org.apache.coyote.http11.Http11Processor.process(org.apache.tomcat.util.net.SocketWrapper) @bci=263, line=203 (Compiled frame) 
- org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(org.apache.tomcat.util.net.SocketWrapper, org.apache.tomcat.util.net.SocketStatus) @bci=96, line=515 (Compiled frame) 
- org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run() @bci=130, line=302 (Compiled frame) 
- java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker) @bci=95, line=1145 (Compiled frame) 
- java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=615 (Interpreted frame) 
- java.lang.Thread.run() @bci=11, line=745 (Interpreted frame) 




Thread 23677 - threadId:Thread 23677 - state:BLOCKED 
stackTrace: 
- sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may be imprecise) 
- java.util.concurrent.locks.LockSupport.parkNanos(java.lang.Object, long) @bci=20, line=226 (Compiled frame) 
- java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(long) @bci=68, line=2082 (Compiled frame) 
- java.util.concurrent.LinkedBlockingQueue.poll(long, java.util.concurrent.TimeUnit) @bci=62, line=467 (Compiled frame) 
- org.apache.tomcat.util.threads.TaskQueue.poll(long, java.util.concurrent.TimeUnit) @bci=3, line=86 (Compiled frame) 
- org.apache.tomcat.util.threads.TaskQueue.poll(long, java.util.concurrent.TimeUnit) @bci=3, line=32 (Compiled frame) 
- java.util.concurrent.ThreadPoolExecutor.getTask() @bci=141, line=1068 (Compiled frame) 
- java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker) @bci=26, line=1130 (Compiled frame) 
- java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=615 (Interpreted frame) 
- java.lang.Thread.run() @bci=11, line=745 (Interpreted frame) 


Thread 23674 - threadId:Thread 23674 - state:BLOCKED 
stackTrace: 
- com.mysql.jdbc.SingleByteCharsetConverter.toString(byte[], int, int) @bci=1, line=322 (Compiled frame) 
- com.mysql.jdbc.ResultSetRow.getString(java.lang.String, com.mysql.jdbc.MySQLConnection, byte[], int, int) @bci=54, line=797 (Compiled frame) 
- com.mysql.jdbc.ByteArrayRow.getString(int, java.lang.String, com.mysql.jdbc.MySQLConnection) @bci=24, line=72 (Compiled frame) 
- com.mysql.jdbc.ResultSetImpl.getStringInternal(int, boolean) @bci=155, line=5699 (Compiled frame) 
- com.mysql.jdbc.ResultSetImpl.getString(int) @bci=3, line=5576 (Compiled frame) 
- com.mysql.jdbc.ResultSetImpl.getString(java.lang.String) @bci=6, line=5616 (Compiled frame) 
- com.mchange.v2.c3p0.impl.NewProxyResultSet.getString(java.lang.String) @bci=19, line=3342 (Compiled frame) 
- org.hibernate.type.StringType.get(java.sql.ResultSet, java.lang.String) @bci=2, line=41 (Compiled frame) 
- org.hibernate.type.NullableType.nullSafeGet(java.sql.ResultSet, java.lang.String) @bci=3, line=184 (Compiled frame) 
- org.hibernate.type.NullableType.nullSafeGet(java.sql.ResultSet, java.lang.String, org.hibernate.engine.SessionImplementor, java.lang.Object) @bci=3, line=210 (Compiled frame) 
+0

嗯,线程转储似乎并不准确。 'Unsafe.park'是一个TIMED_WAITING,并且socket.read正在等待。你能通过'kill -3 '生成一个线程转储吗?它将包含阻塞线程的对象的地址,因此您可以检查是否存在死锁。 – bashnesnos

回答

1
  • 首先堆栈跟踪表明线程试图从套接字读取走进BLOCKED状态。套接字读取操作是一个阻塞操作,这意味着如果没有什么要读取或者直到所有的信息都被完全读取,它将被阻塞。

  • 其次,LinkedBlockingQueue.poll()不是一个阻塞操作,所以这是一个正常的堆栈跟踪来指示通常的空闲线程。这不是由用户代码造成的

  • 第三,由于返回结果集中的字符串值,这也不会造成问题。

我想,你应该看看this了。

堆栈跟踪#1和#3可能相关,因为套接字读取可能是数据库读取。

这些堆栈跟踪不会帮助解决问题,但是这些被阻塞的线程只是表示内存过多和垃圾收集过多的问题。

您的C3P0池可能存在问题,或者您可能会创建语句和结果集对象 - 总而言之,这似乎是内存泄漏和资源关闭不良的情况。

如果没有相关的应用程序代码,非常精确的答案是不可能的。另外,如评论中所述,锁定对象的身份也需要转储。

希望它有帮助!