因此,我继承了一些代码,它们正在等待来自网络源的通信。Java Thread.sleep泄漏线程?
当它正在等待来自网络套接字的更多数据时,Thread.sleep(10)
被调用。这似乎是导致线程泄漏,如JConsole的报道,在这里我的线程转储(也有数百个条目的主题-68,螺纹385,等...但我缩短了简洁):
Wed Jan 18 09:14:40 PST 2012
2012-01-18 09:14:50
Full thread dump Java HotSpot(TM) 64-Bit Server VM (20.0-b11 mixed mode):
"Thread-69" daemon prio=10 tid=0x00007f01a047c800 nid=0x3725 waiting on condition [0x00007f019eaf4000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at com.unitt.framework.websocket.simple.NetworkSocket.run(NetworkSocket.java:304)
at java.lang.Thread.run(Thread.java:662)
"Thread-68" daemon prio=10 tid=0x00007f01a0500000 nid=0x371c waiting on condition [0x00007f019ecf6000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at com.unitt.framework.websocket.simple.NetworkSocket.run(NetworkSocket.java:304)
at java.lang.Thread.run(Thread.java:662)
有问题的代码:
public class NetworkSocket implements NetworkSocketFacade, Runnable
{
... removed many irrelevant methods
public void run()
{
byte[] readBuffer = new byte[512 * 1024];
while (isRunning)
{
//ioLogger.debug("in while(isRunning) loop");
try
{
int length = input.available();
if (length > 0)
{
int read = input.read(readBuffer, 0, readBuffer.length);
if (read < 0)
{
isRunning = false;
//@todo: do we disconnect?
ioLogger.debug("setting isRunning FALSE after read < 0");
}
else
{
//read data and process
}
}
else
{
//ioLogger.debug("nothing to read, sleeping");
try
{
Thread.sleep(10);
}
catch (InterruptedException e)
{
//do nothing, keep going
}
}
}
// some catch blocks and logging after this
我有一些担心调用sleep这个频率可能会出现问题,我已经试过增加10至250的睡眠时间只是为了缓和局势。这确实有助于改善问题,但随着时间的推移,我仍然会遇到同样的问题 - 我稳定地泄漏线程,直到我离开堆空间。
有没有人有任何见解这种行为?我不认为像Thread.sleep()
那样基本的东西会导致这样的问题。
这种“线程泄漏”的假设机制是什么? 'Thread.sleep()'永不返回? – NPE 2012-01-18 17:45:54
当我看着我的jconsole线数时,我不确定还有什么叫它,它以30度的角度攀爬了18个小时。新线程不断创建,所有旧线程都停留在上面列出的“等待状态”位置。 – AWT 2012-01-18 17:54:52