发生死锁的线程dump日志_jvm死锁时生成dump日志-优快云博客

本文链接：https://blog.youkuaiyun.com/fangleijiang/article/details/78964710

本文展示了一个具体的Java死锁情况，详细记录了两个线程如何因互相等待对方持有的锁而形成死锁。通过分析线程堆栈信息及锁定的同步器，揭示了解决此类问题的方法。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

注意日志里面的红色加粗的日志

"Thread-1" prio=6 tid=0x000000000d3d3000 nid=0x3414 waiting for monitor entry [0x000000000cc5f000]
java.lang.Thread.State: BLOCKED (on object monitor)
at Deadlocker$Thread2.run(Deadlocker.java:37)
- waiting to lock <0x00000007d5d9b500> (a [I)
- locked <0x00000007d5d9b518> (a [I)

Locked ownable synchronizers:
- None

"Thread-0" prio=6 tid=0x000000000d3d0000 nid=0x30cc waiting for monitor entry [0x000000000db9f000]
java.lang.Thread.State: BLOCKED (on object monitor)
at Deadlocker$Thread1.run(Deadlocker.java:18)
- waiting to lock <0x00000007d5d9b518> (a [I)
- locked <0x00000007d5d9b500> (a [I)

Locked ownable synchronizers:
- None

Found one Java-level deadlock:
=============================
"Thread-1":
waiting to lock monitor 0x000000000b813448 (object 0x00000007d5d9b500, a [I),
which is held by "Thread-0"
"Thread-0":
waiting to lock monitor 0x000000000b814628 (object 0x00000007d5d9b518, a [I),
which is held by "Thread-1"

Java stack information for the threads listed above:
===================================================
"Thread-1":
at Deadlocker$Thread2.run(Deadlocker.java:37)
- waiting to lock <0x00000007d5d9b500> (a [I)
- locked <0x00000007d5d9b518> (a [I)
"Thread-0":
at Deadlocker$Thread1.run(Deadlocker.java:18)
- waiting to lock<0x00000007d5d9b518> (a [I)
- locked <0x00000007d5d9b500> (a [I)

Found 1 deadlock.