死鎖定位

  • 運行可以產(chǎn)生死鎖的程序
  • 在cmd中輸入jdk自帶的 jps -l命令(類似于linux中的ps -ef|grep xxx),根據(jù)打印結(jié)果獲取死鎖進程編號
  • 使用jstack -進程號就可以看到具體的原因烫扼。
    demo
C:\Users\Limer>jps
1140 Jps
15140 Deadlock
8964
10344 jar
6680 Launcher

C:\Users\Limer>jstack 15140
2019-11-02 18:25:21
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.211-b12 mixed mode):

"DestroyJavaVM" #13 prio=5 os_prio=0 tid=0x0000000002802800 nid=0x3bc0 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"threadB" #12 prio=5 os_prio=0 tid=0x0000000018899000 nid=0x3b80 waiting for monitor entry [0x000000001957f000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at com.lhp.MyHoldThread.run(Deadlock.java:29)
        - waiting to lock <0x00000000d60c43d8> (a java.lang.String)
        - locked <0x00000000d60c4410> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)

"threadA" #11 prio=5 os_prio=0 tid=0x0000000018896000 nid=0x3b40 waiting for monitor entry [0x000000001947e000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at com.lhp.MyHoldThread.run(Deadlock.java:29)
        - waiting to lock <0x00000000d60c4410> (a java.lang.String)
        - locked <0x00000000d60c43d8> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)

"Service Thread" #10 daemon prio=9 os_prio=0 tid=0x0000000018857800 nid=0x31f8 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C1 CompilerThread2" #9 daemon prio=9 os_prio=2 tid=0x00000000187c9800 nid=0x36d8 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread1" #8 daemon prio=9 os_prio=2 tid=0x00000000187c8800 nid=0x38bc waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread0" #7 daemon prio=9 os_prio=2 tid=0x00000000187c5000 nid=0x1de8 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Monitor Ctrl-Break" #6 daemon prio=5 os_prio=0 tid=0x00000000187c2800 nid=0x13d0 runnable [0x0000000018e7e000]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        - locked <0x00000000d610d6e0> (a java.io.InputStreamReader)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.fill(BufferedReader.java:161)
        at java.io.BufferedReader.readLine(BufferedReader.java:324)
        - locked <0x00000000d610d6e0> (a java.io.InputStreamReader)
        at java.io.BufferedReader.readLine(BufferedReader.java:389)
        at com.intellij.rt.execution.application.AppMainV2$1.run(AppMainV2.java:64)

"Attach Listener" #5 daemon prio=5 os_prio=2 tid=0x0000000017476800 nid=0x3a94 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" #4 daemon prio=9 os_prio=2 tid=0x0000000018790800 nid=0x13d4 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Finalizer" #3 daemon prio=8 os_prio=1 tid=0x00000000028f7000 nid=0x3594 in Object.wait() [0x000000001877f000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000000d5f88ed0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
        - locked <0x00000000d5f88ed0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:216)

"Reference Handler" #2 daemon prio=10 os_prio=2 tid=0x000000001740a000 nid=0x3a8c in Object.wait() [0x000000001867f000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000000d5f86bf8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:502)
        at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
        - locked <0x00000000d5f86bf8> (a java.lang.ref.Reference$Lock)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

"VM Thread" os_prio=2 tid=0x00000000173e6800 nid=0x30b4 runnable

"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x0000000002818000 nid=0x3afc runnable

"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x0000000002819800 nid=0x1148 runnable

"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x000000000281b800 nid=0x20a8 runnable

"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x000000000281d000 nid=0x3978 runnable

"VM Periodic Task Thread" os_prio=2 tid=0x0000000018893000 nid=0xcb0 waiting on condition

JNI global references: 12


Found one Java-level deadlock:
=============================
"threadB":
  waiting to lock monitor 0x0000000017410708 (object 0x00000000d60c43d8, a java.lang.String),
  which is held by "threadA"
"threadA":
  waiting to lock monitor 0x000000001740dd18 (object 0x00000000d60c4410, a java.lang.String),
  which is held by "threadB"

Java stack information for the threads listed above:
===================================================
"threadB":
        at com.lhp.MyHoldThread.run(Deadlock.java:29)
        - waiting to lock <0x00000000d60c43d8> (a java.lang.String)
        - locked <0x00000000d60c4410> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)
"threadA":
        at com.lhp.MyHoldThread.run(Deadlock.java:29)
        - waiting to lock <0x00000000d60c4410> (a java.lang.String)
        - locked <0x00000000d60c43d8> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)

Found 1 deadlock.

?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 序言:七十年代末艺普,一起剝皮案震驚了整個濱河市,隨后出現(xiàn)的幾起案子厉亏,更是在濱河造成了極大的恐慌,老刑警劉巖,帶你破解...
    沈念sama閱讀 217,907評論 6 506
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件族铆,死亡現(xiàn)場離奇詭異,居然都是意外死亡哭尝,警方通過查閱死者的電腦和手機哥攘,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 92,987評論 3 395
  • 文/潘曉璐 我一進店門,熙熙樓的掌柜王于貴愁眉苦臉地迎上來材鹦,“玉大人逝淹,你說我怎么就攤上這事⊥疤疲” “怎么了栅葡?”我有些...
    開封第一講書人閱讀 164,298評論 0 354
  • 文/不壞的土叔 我叫張陵,是天一觀的道長尤泽。 經(jīng)常有香客問我欣簇,道長,這世上最難降的妖魔是什么坯约? 我笑而不...
    開封第一講書人閱讀 58,586評論 1 293
  • 正文 為了忘掉前任熊咽,我火速辦了婚禮,結(jié)果婚禮上闹丐,老公的妹妹穿的比我還像新娘横殴。我一直安慰自己,他們只是感情好卿拴,可當我...
    茶點故事閱讀 67,633評論 6 392
  • 文/花漫 我一把揭開白布衫仑。 她就那樣靜靜地躺著梨与,像睡著了一般。 火紅的嫁衣襯著肌膚如雪文狱。 梳的紋絲不亂的頭發(fā)上粥鞋,一...
    開封第一講書人閱讀 51,488評論 1 302
  • 那天,我揣著相機與錄音瞄崇,去河邊找鬼陷虎。 笑死,一個胖子當著我的面吹牛杠袱,可吹牛的內(nèi)容都是我干的尚猿。 我是一名探鬼主播,決...
    沈念sama閱讀 40,275評論 3 418
  • 文/蒼蘭香墨 我猛地睜開眼楣富,長吁一口氣:“原來是場噩夢啊……” “哼凿掂!你這毒婦竟也來了?” 一聲冷哼從身側(cè)響起纹蝴,我...
    開封第一講書人閱讀 39,176評論 0 276
  • 序言:老撾萬榮一對情侶失蹤庄萎,失蹤者是張志新(化名)和其女友劉穎,沒想到半個月后塘安,有當?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體糠涛,經(jīng)...
    沈念sama閱讀 45,619評論 1 314
  • 正文 獨居荒郊野嶺守林人離奇死亡,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點故事閱讀 37,819評論 3 336
  • 正文 我和宋清朗相戀三年兼犯,在試婚紗的時候發(fā)現(xiàn)自己被綠了忍捡。 大學時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片。...
    茶點故事閱讀 39,932評論 1 348
  • 序言:一個原本活蹦亂跳的男人離奇死亡切黔,死狀恐怖砸脊,靈堂內(nèi)的尸體忽然破棺而出,到底是詐尸還是另有隱情纬霞,我是刑警寧澤凌埂,帶...
    沈念sama閱讀 35,655評論 5 346
  • 正文 年R本政府宣布,位于F島的核電站诗芜,受9級特大地震影響瞳抓,放射性物質(zhì)發(fā)生泄漏。R本人自食惡果不足惜伏恐,卻給世界環(huán)境...
    茶點故事閱讀 41,265評論 3 329
  • 文/蒙蒙 一孩哑、第九天 我趴在偏房一處隱蔽的房頂上張望。 院中可真熱鬧脐湾,春花似錦臭笆、人聲如沸。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,871評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽。三九已至闻鉴,卻和暖如春茵乱,著一層夾襖步出監(jiān)牢的瞬間,已是汗流浹背孟岛。 一陣腳步聲響...
    開封第一講書人閱讀 32,994評論 1 269
  • 我被黑心中介騙來泰國打工瓶竭, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留,地道東北人渠羞。 一個月前我還...
    沈念sama閱讀 48,095評論 3 370
  • 正文 我出身青樓斤贰,卻偏偏與公主長得像,于是被迫代替她去往敵國和親次询。 傳聞我的和親對象是個殘疾皇子荧恍,可洞房花燭夜當晚...
    茶點故事閱讀 44,884評論 2 354

推薦閱讀更多精彩內(nèi)容