查找死锁发生的位置

查看本机jvm进程(运行了Test类中的main方法)

D:\soft\Java\jdk1.8.0_131\bin>jps
2516
6756 Launcher
6820 Jps
2472 Test
8424
找到了Test进程id为:2472

jstack命令查看当前线程堆栈调用情况

D:\soft\Java\jdk1.8.0_131\bin>jstack
Usage:
jstack [-l] <pid>
(to connect to running process)
jstack -F [-m] [-l] <pid>
(to connect to a hung process)
jstack [-m] [-l] <executable> <core>
(to connect to a core file)
jstack [-m] [-l] [server_id@]<remote server IP or hostname>
(to connect to a remote debug server)

Options:
-F to force a thread dump. Use when jstack <pid> does not respond (process is hung)
-m to print both java and native frames (mixed mode)
-l long listing. Prints additional information about locks
-h or -help to print this help message

D:\soft\Java\jdk1.8.0_131\bin>jstack 2472
2019-11-11 13:58:51
Full thread dump OpenJDK 64-Bit Server VM (11.0.3+12-b304.56 mixed mode, sharing):

Threads class SMR info:
_java_thread_list=0x00000247257519f0, length=13, elements={
0x0000024724cf8800, 0x0000024724cf9800, 0x0000024724d1b000, 0x0000024724d1c000,
0x0000024724d1d800, 0x0000024724d2a800, 0x0000024724d2f800, 0x0000024724cdd800,
0x000002472575b800, 0x000002472575c800, 0x0000024725772800, 0x0000024725777800,
0x0000024709de6000
}

"Reference Handler" #2 daemon prio=10 os_prio=2 cpu=0.00ms elapsed=114.56s tid=0x0000024724cf8800 nid=0x9bc waiting on condition [0x000000d1bb5fe000]
java.lang.Thread.State: RUNNABLE
at java.lang.ref.Reference.waitForReferencePendingList(java.base@11.0.3/Native Method)
at java.lang.ref.Reference.processPendingReferences(java.base@11.0.3/Reference.java:241)
at java.lang.ref.Reference$ReferenceHandler.run(java.base@11.0.3/Reference.java:213)

"Finalizer" #3 daemon prio=8 os_prio=1 cpu=0.00ms elapsed=114.56s tid=0x0000024724cf9800 nid=0x24b0 in Object.wait() [0x000000d1bb6fe000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(java.base@11.0.3/Native Method)
- waiting on <0x0000000089f0a2b0> (a java.lang.ref.ReferenceQueueLock) at java.lang.ref.ReferenceQueue.remove(java.base@11.0.3/ReferenceQueue.java:155) - waiting to re-lock in wait() <0x0000000089f0a2b0> (a java.lang.ref.ReferenceQueueLock)
at java.lang.ref.ReferenceQueue.remove(java.base@11.0.3/ReferenceQueue.java:176)
at java.lang.ref.Finalizer$FinalizerThread.run(java.base@11.0.3/Finalizer.java:170)

"Signal Dispatcher" #4 daemon prio=9 os_prio=2 cpu=0.00ms elapsed=114.55s tid=0x0000024724d1b000 nid=0x21d8 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Attach Listener" #5 daemon prio=5 os_prio=2 cpu=15.63ms elapsed=114.55s tid=0x0000024724d1c000 nid=0x2a4 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"C2 CompilerThread0" #6 daemon prio=9 os_prio=2 cpu=46.88ms elapsed=114.55s tid=0x0000024724d1d800 nid=0x5c0 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
No compile task

"C1 CompilerThread0" #9 daemon prio=9 os_prio=2 cpu=78.13ms elapsed=114.55s tid=0x0000024724d2a800 nid=0x448 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
No compile task

"Sweeper thread" #10 daemon prio=9 os_prio=2 cpu=0.00ms elapsed=114.55s tid=0x0000024724d2f800 nid=0xa84 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Common-Cleaner" #11 daemon prio=8 os_prio=1 cpu=0.00ms elapsed=114.52s tid=0x0000024724cdd800 nid=0x1c54 in Object.wait() [0x000000d1bbcfe000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(java.base@11.0.3/Native Method)
- waiting on <0x0000000089e2bca8> (a java.lang.ref.ReferenceQueueLock) at java.lang.ref.ReferenceQueue.remove(java.base@11.0.3/ReferenceQueue.java:155) - waiting to re-lock in wait() <0x0000000089e2bca8> (a java.lang.ref.ReferenceQueueLock)
at jdk.internal.ref.CleanerImpl.run(java.base@11.0.3/CleanerImpl.java:148)
at java.lang.Thread.run(java.base@11.0.3/Thread.java:834)
at jdk.internal.misc.InnocuousThread.run(java.base@11.0.3/InnocuousThread.java:134)

"Monitor Ctrl-Break" #12 daemon prio=5 os_prio=0 cpu=15.63ms elapsed=114.48s tid=0x000002472575b800 nid=0x24e8 runnable [0x000000d1bbefe000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(java.base@11.0.3/Native Method)
at java.net.SocketInputStream.socketRead(java.base@11.0.3/SocketInputStream.java:115)
at java.net.SocketInputStream.read(java.base@11.0.3/SocketInputStream.java:168)
at java.net.SocketInputStream.read(java.base@11.0.3/SocketInputStream.java:140)
at sun.nio.cs.StreamDecoder.readBytes(java.base@11.0.3/StreamDecoder.java:284)
at sun.nio.cs.StreamDecoder.implRead(java.base@11.0.3/StreamDecoder.java:326)
at sun.nio.cs.StreamDecoder.read(java.base@11.0.3/StreamDecoder.java:178)
- locked <0x0000000089b061b0> (a java.io.InputStreamReader)
at java.io.InputStreamReader.read(java.base@11.0.3/InputStreamReader.java:185)
at java.io.BufferedReader.fill(java.base@11.0.3/BufferedReader.java:161)
at java.io.BufferedReader.readLine(java.base@11.0.3/BufferedReader.java:326)
- locked <0x0000000089b061b0> (a java.io.InputStreamReader)
at java.io.BufferedReader.readLine(java.base@11.0.3/BufferedReader.java:392)
at com.intellij.rt.execution.application.AppMainV2$1.run(AppMainV2.java:64)

"Service Thread" #13 daemon prio=9 os_prio=0 cpu=0.00ms elapsed=114.48s tid=0x000002472575c800 nid=0x1370 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-1" #14 prio=5 os_prio=0 cpu=15.63ms elapsed=114.48s tid=0x0000024725772800 nid=0x25e0 waiting for monitor entry [0x000000d1bc1ff000]
java.lang.Thread.State: BLOCKED (on object monitor)
at deadlock.Target.method1(Target.java:18)
- waiting to lock <0x0000000089d903a8> (a java.lang.Object)
- locked <0x0000000089d90398> (a java.lang.Object)
at deadlock.Target.run(Target.java:41)
at java.lang.Thread.run(java.base@11.0.3/Thread.java:834)

"Thread-2" #15 prio=5 os_prio=0 cpu=15.63ms elapsed=114.48s tid=0x0000024725777800 nid=0x408 waiting for monitor entry [0x000000d1bc2fe000]
java.lang.Thread.State: BLOCKED (on object monitor)
at deadlock.Target.method2(Target.java:32)
- waiting to lock <0x0000000089d90398> (a java.lang.Object)
- locked <0x0000000089d903a8> (a java.lang.Object)
at deadlock.Target.run(Target.java:43)
at java.lang.Thread.run(java.base@11.0.3/Thread.java:834)

"DestroyJavaVM" #16 prio=5 os_prio=0 cpu=109.38ms elapsed=114.48s tid=0x0000024709de6000 nid=0x25cc waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"VM Thread" os_prio=2 cpu=0.00ms elapsed=114.56s tid=0x0000024724cf7000 nid=0x1e78 runnable

"GC Thread#0" os_prio=2 cpu=0.00ms elapsed=114.58s tid=0x0000024709dfe800 nid=0xd84 runnable

"G1 Main Marker" os_prio=2 cpu=0.00ms elapsed=114.58s tid=0x0000024709e30800 nid=0x2520 runnable

"G1 Conc#0" os_prio=2 cpu=0.00ms elapsed=114.58s tid=0x0000024709e32000 nid=0x1d64 runnable

"G1 Refine#0" os_prio=2 cpu=0.00ms elapsed=114.58s tid=0x0000024724b90800 nid=0x1268 runnable

"G1 Young RemSet Sampling" os_prio=2 cpu=0.00ms elapsed=114.58s tid=0x0000024724b91800 nid=0x794 runnable
"VM Periodic Task Thread" os_prio=2 cpu=0.00ms elapsed=114.48s tid=0x000002472576d800 nid=0x1454 waiting on condition

JNI global refs: 16, weak refs: 0

Found one Java-level deadlock:

"Thread-1":
waiting to lock monitor 0x0000024724d0b500 (object 0x0000000089d903a8, a java.lang.Object),
which is held by "Thread-2"
"Thread-2":
waiting to lock monitor 0x0000024724d09100 (object 0x0000000089d90398, a java.lang.Object),
which is held by "Thread-1"

Java stack information for the threads listed above:

"Thread-1":
at deadlock.Target.method1(Target.java:18)
- waiting to lock <0x0000000089d903a8> (a java.lang.Object)
- locked <0x0000000089d90398> (a java.lang.Object)
at deadlock.Target.run(Target.java:41)
at java.lang.Thread.run(java.base@11.0.3/Thread.java:834)
"Thread-2":
at deadlock.Target.method2(Target.java:32)
- waiting to lock <0x0000000089d90398> (a java.lang.Object)
- locked <0x0000000089d903a8> (a java.lang.Object)
at deadlock.Target.run(Target.java:43)
at java.lang.Thread.run(java.base@11.0.3/Thread.java:834)

Found 1 deadlock.

method1和method2存在死锁

©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 194,524评论 5 460
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 81,869评论 2 371
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 141,813评论 0 320
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 52,210评论 1 263
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 61,085评论 4 355
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 46,117评论 1 272
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 36,533评论 3 381
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 35,219评论 0 253
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 39,487评论 1 290
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 34,582评论 2 309
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 36,362评论 1 326
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 32,218评论 3 312
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 37,589评论 3 299
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 28,899评论 0 17
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 30,176评论 1 250
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 41,503评论 2 341
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 40,707评论 2 335

推荐阅读更多精彩内容