Java线程转储:"WAITING(在对象监视器上)"行,而不是“在< 0x1234>"行上等待 [英] Java thread dump: `WAITING (on object monitor)` line not followed by `waiting on <0x1234>` line

查看:303
本文介绍了Java线程转储:"WAITING(在对象监视器上)"行,而不是“在< 0x1234>"行上等待的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的线程TP-Processor27正在等待,告诉我一个线程转储.

My thread TP-Processor27 is waiting, tells me a thread dump.

通常在WAITING (on object monitor)行之后紧接着是waiting on <0x09c34480>或类似行.但不在下面的转储中.在这种情况下,我可以知道等待哪个ID吗?

Usually WAITING (on object monitor) lines are immediately followed by a waiting on <0x09c34480> or similar line. But not in the dump below. In such cases, can I know on which id is the wait?

"TP-Processor27" daemon prio=10 tid=0x00002aab91c88800 nid=0x58d7 in Object.wait() [0x0000000050d01000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:485)
        at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1104)
        - locked <0x00002aaaccce0150> (a org.apache.commons.pool.impl.GenericObjectPool$Latch)
        at org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:88)
        at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:115)
        at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1053)
[...]

"TP-Processor28" daemon prio=10 tid=0x00002aab91c8a000 nid=0x58d8 runnable [0x0000000050e03000]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
[...]

推荐答案

似乎我看到了实际上没有问题的问题.

It seems that I saw a problem where there is actually no problem.

这篇关于Java线程转储:"WAITING(在对象监视器上)"行,而不是“在&lt; 0x1234&gt;"行上等待的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆