这类似于Java thread dump: BLOCKED thread without “waiting to lock …”.
基本上,我看到了一个BLOCKED线程,但是它具有等待的锁:
"pool-1-thread-60" prio=10 tid=0x00007fbf10017000 nid=0x210 waiting for monitor entry [0x00007fbed64e3000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.Category.callAppenders(Category.java:204)
- locked <0x0000000742444ad0> (a org.apache.log4j.Logger)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.info(Category.java:666)
...
我希望看到-等待锁定< 0x0000000742444ad0> …而不是-锁定….另一个问题表明是垃圾回收的原因,但是如果那样的话,不是所有线程都被阻塞了吗?还有其他线程是可运行的.另外,我怎么能证明是这种情况?为什么这是观察到的行为?我不想盲目地假设它是垃圾收集器,只是几天后才发现它是其他东西.
==辅助信息==
尽管我认为与当前问题无关,但这是上述转储来自的代码部分.
for(Category c = this; c != null; c=c.parent) {
// Protected against simultaneous call to addAppender, removeAppender,...
synchronized(c) { //line 204
if(c.aai != null) {
writes += c.aai.appendLoopOnAppenders(event);
}
if(!c.additive) {
break;
}
}
}
显然,在那条线上需要获得一个锁.但是,当线程在此监视器上真正被阻塞时,线程转储中的输出看起来像(来自同一转储):
"pool-1-thread-44" prio=10 tid=0x00007fbef0051000 nid=0x200 waiting for monitor\n entry [0x00007fbed74f3000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.Category.callAppenders(Category.java:204)
- waiting to lock <0x0000000742444ad0> (a org.apache.log4j.Logger)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.info(Category.java:666)
...
我感兴趣的转储部分看起来有所不同(“锁定”而不是“等待锁定”).我调试了许多死锁,并查看了许多线程转储.我总是看到的是“等待锁定”.我从未见过“锁定”线程,但仍“等待监视器进入”线程,我想知道这意味着什么.