Java最终效果线被阻止

发布于 2025-01-26 13:08:36 字数 4492 浏览 1 评论 0原文

Java的大量线程处于阻塞状态,正在等待锁,但是没有线程可以让此锁

blocked螺纹

[root@xxx xxx]# grep BLOCKED 11.txt -C5
    at java.lang.ref.Reference.waitForReferencePendingList([email protected]/Native Method)
    at java.lang.ref.Reference.processPendingReferences([email protected]/Reference.java:241)
    at java.lang.ref.Reference$ReferenceHandler.run([email protected]/Reference.java:213)

"Finalizer" #3 daemon prio=8 os_prio=0 cpu=273.67ms elapsed=1139.36s tid=0x00007fabf2c6a000 nid=0x11 waiting for monitor entry  [0x00007fabb19fd000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at java.lang.ref.Finalizer.runFinalizer([email protected]/Finalizer.java:70)
    - waiting to lock <0x000000048046f6f0> (a java.lang.Object)
    at java.lang.ref.Finalizer$FinalizerThread.run([email protected]/Finalizer.java:171)

"Signal Dispatcher" #4 daemon prio=9 os_prio=0 cpu=1.42ms elapsed=1139.36s tid=0x00007fabf2c6b000 nid=0x12 runnable  [0x0000000000000000]
--
    at java.util.concurrent.LinkedBlockingQueue.take([email protected]/LinkedBlockingQueue.java:433)
    at com.alipay.remoting.ReconnectManager$HealConnectionRunner.run(ReconnectManager.java:144)
    at java.lang.Thread.run([email protected]/Thread.java:835)

"Init-TX-Disruptor-0" #26 prio=5 os_prio=0 cpu=4732.71ms elapsed=1122.35s tid=0x00007fabb40c5800 nid=0x5d waiting for monitor entry  [0x00007fab939ec000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at java.lang.ref.Finalizer.<init>([email protected]/Finalizer.java:51)
    - waiting to lock <0x000000048046f6f0> (a java.lang.Object)
    at java.lang.ref.Finalizer.register([email protected]/Finalizer.java:66)
    at java.lang.Object.<init>([email protected]/Object.java:50)
    at org.rocksdb.AbstractNativeReference.<init>(AbstractNativeReference.java:25)
--
    at xx.xxxx.xxx.xx.xxxx.xx.xx.onEvent(InitTxWorkHandler.java:24)
    at com.lmax.disruptor.WorkProcessor.run(WorkProcessor.java:143)
    at java.lang.Thread.run([email protected]/Thread.java:835)

"Init-TX-Disruptor-1" #27 prio=5 os_prio=0 cpu=4698.53ms elapsed=1122.35s tid=0x00007faba7b1a000 nid=0x5e waiting for monitor entry  [0x00007fab9236b000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at java.lang.ref.Finalizer.<init>([email protected]/Finalizer.java:51)
    - waiting to lock <0x000000048046f6f0> (a java.lang.Object)
    at java.lang.ref.Finalizer.register([email protected]/Finalizer.java:66)
    at java.lang.Object.<init>([email protected]/Object.java:50)
    at org.rocksdb.AbstractNativeReference.<init>(AbstractNativeReference.java:25)


0x000000048046f6f0找不到拥有的监视器,请访问0x000000048046f6f6f0

GREP 已经被阻塞了很长时间了,我想知道为什么

Java's large number of threads are in a blocked state, waiting for a lock, but there is no thread to have this lock

blocked thread

[root@xxx xxx]# grep BLOCKED 11.txt -C5
    at java.lang.ref.Reference.waitForReferencePendingList([email protected]/Native Method)
    at java.lang.ref.Reference.processPendingReferences([email protected]/Reference.java:241)
    at java.lang.ref.Reference$ReferenceHandler.run([email protected]/Reference.java:213)

"Finalizer" #3 daemon prio=8 os_prio=0 cpu=273.67ms elapsed=1139.36s tid=0x00007fabf2c6a000 nid=0x11 waiting for monitor entry  [0x00007fabb19fd000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at java.lang.ref.Finalizer.runFinalizer([email protected]/Finalizer.java:70)
    - waiting to lock <0x000000048046f6f0> (a java.lang.Object)
    at java.lang.ref.Finalizer$FinalizerThread.run([email protected]/Finalizer.java:171)

"Signal Dispatcher" #4 daemon prio=9 os_prio=0 cpu=1.42ms elapsed=1139.36s tid=0x00007fabf2c6b000 nid=0x12 runnable  [0x0000000000000000]
--
    at java.util.concurrent.LinkedBlockingQueue.take([email protected]/LinkedBlockingQueue.java:433)
    at com.alipay.remoting.ReconnectManager$HealConnectionRunner.run(ReconnectManager.java:144)
    at java.lang.Thread.run([email protected]/Thread.java:835)

"Init-TX-Disruptor-0" #26 prio=5 os_prio=0 cpu=4732.71ms elapsed=1122.35s tid=0x00007fabb40c5800 nid=0x5d waiting for monitor entry  [0x00007fab939ec000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at java.lang.ref.Finalizer.<init>([email protected]/Finalizer.java:51)
    - waiting to lock <0x000000048046f6f0> (a java.lang.Object)
    at java.lang.ref.Finalizer.register([email protected]/Finalizer.java:66)
    at java.lang.Object.<init>([email protected]/Object.java:50)
    at org.rocksdb.AbstractNativeReference.<init>(AbstractNativeReference.java:25)
--
    at xx.xxxx.xxx.xx.xxxx.xx.xx.onEvent(InitTxWorkHandler.java:24)
    at com.lmax.disruptor.WorkProcessor.run(WorkProcessor.java:143)
    at java.lang.Thread.run([email protected]/Thread.java:835)

"Init-TX-Disruptor-1" #27 prio=5 os_prio=0 cpu=4698.53ms elapsed=1122.35s tid=0x00007faba7b1a000 nid=0x5e waiting for monitor entry  [0x00007fab9236b000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at java.lang.ref.Finalizer.<init>([email protected]/Finalizer.java:51)
    - waiting to lock <0x000000048046f6f0> (a java.lang.Object)
    at java.lang.ref.Finalizer.register([email protected]/Finalizer.java:66)
    at java.lang.Object.<init>([email protected]/Object.java:50)
    at org.rocksdb.AbstractNativeReference.<init>(AbstractNativeReference.java:25)


grep 0x000000048046f6f0 not found owns the monitor on 0x000000048046f6f0

grep 0x000000048046f6f0

The thread has been blocked for a long time, I want to know why

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文