Java程序死鎖，3種方式快速找到死鎖代碼

時間  2019-11-11
標籤 java 程序 死鎖 方式 快速 找到 代碼 欄目 Java 简体版
原文   原文鏈接

java程序中出現死鎖問題，若是不瞭解排查方法，是一籌莫展的，今天我們用三種方法找到死鎖問題。java

運行下面代碼

package com.jvm.visualvm;

/**
 * <a href="http://www.itsoku.com/archives">Java乾貨鋪子,只生產乾貨，公衆號：javacode2018</a>
 */
public class Demo4 {

    public static void main(String[] args) {
        User u1 = new User("u1");
        User u2 = new User("u2");
        Thread thread1 = new Thread(new SynAddRunalbe(u1, u2, 1, 2, true));
        thread1.setName("thread1");
        thread1.start();
        Thread thread2 = new Thread(new SynAddRunalbe(u1, u2, 2, 1, false));
        thread2.setName("thread2");
        thread2.start();
    }

    /**
     * 線程死鎖等待演示
     */
    public static class SynAddRunalbe implements Runnable {
        User u1, u2;
        int a, b;
        boolean flag;

        public SynAddRunalbe(User u1, User u2, int a, int b, boolean flag) {
            this.u1 = u1;
            this.u2 = u2;
            this.a = a;
            this.b = b;
            this.flag = flag;
        }

        @Override
        public void run() {
            try {
                if (flag) {
                    synchronized (u1) {
                        Thread.sleep(100);
                        synchronized (u2) {
                            System.out.println(a + b);
                        }
                    }
                } else {
                    synchronized (u2) {
                        Thread.sleep(100);
                        synchronized (u1) {
                            System.out.println(a + b);
                        }
                    }
                }
            } catch (InterruptedException e) {
                e.printStackTrace();
            }
        }
    }

    public static class User {
        private String name;

        public String getName() {
            return name;
        }

        public void setName(String name) {
            this.name = name;
        }

        public User(String name) {
            this.name = name;
        }

        @Override
        public String toString() {
            return "User{" +
                    "name='" + name + '\'' +
                    '}';
        }
    }
}

程序中：thread1持有u1的鎖，thread2持有u2的鎖，thread1等待獲取u2的鎖，thread2等待獲取u1的鎖，相互須要獲取的鎖都被對方持有者，形成了死鎖。程序運行中一直沒法結束。app

經過jdk工具jps、jstack排查死鎖問題 jps、jstack都是jdk提供的命令工具，方便用戶排查程序的一些問題。更詳細的用法見文檔最後。jvm

步驟一：使用jsp查找程序進行 jps：jdk提供的一個工具，能夠查看到正在運行的java進程socket

C:\Users\Think>jps -l
5824 com.jvm.visualvm.Demo4

步驟二：使用jstack查看線程堆棧信息 jstack：jdk提供的一個工具，能夠查看java進程中線程堆棧信息。更詳細的用法見文檔最後。jsp

C:\Users\Think>jstack 5824
2019-06-04 15:34:37
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode):

"DestroyJavaVM" #14 prio=5 os_prio=0 tid=0x0000000002cf4000 nid=0x9fd8 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"thread2" #13 prio=5 os_prio=0 tid=0x000000002884d800 nid=0x40c4 waiting for monitor entry [0x00000000292ce000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at com.jvm.visualvm.Demo4$SynAddRunalbe.run(Demo4.java:49)
        - waiting to lock <0x00000007173d4178> (a com.jvm.visualvm.Demo4$User)
        - locked <0x00000007173d41b8> (a com.jvm.visualvm.Demo4$User)
        at java.lang.Thread.run(Thread.java:745)

"thread1" #12 prio=5 os_prio=0 tid=0x000000002885b800 nid=0x99c0 waiting for monitor entry [0x00000000291cf000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at com.jvm.visualvm.Demo4$SynAddRunalbe.run(Demo4.java:42)
        - waiting to lock <0x00000007173d41b8> (a com.jvm.visualvm.Demo4$User)
        - locked <0x00000007173d4178> (a com.jvm.visualvm.Demo4$User)
        at java.lang.Thread.run(Thread.java:745)

"Service Thread" #11 daemon prio=9 os_prio=0 tid=0x0000000027dd9000 nid=0x7f80 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C1 CompilerThread3" #10 daemon prio=9 os_prio=2 tid=0x0000000027d80800 nid=0x3b94 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

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

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

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

"Monitor Ctrl-Break" #6 daemon prio=5 os_prio=0 tid=0x0000000027d0a800 nid=0x647c runnable [0x00000000282ce000]
   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 <0x0000000717449cd8> (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 <0x0000000717449cd8> (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=0x0000000027b61000 nid=0x7cf8 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

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

"Finalizer" #3 daemon prio=8 os_prio=1 tid=0x0000000027af1800 nid=0x9960 in Object.wait() [0x0000000027fce000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x0000000717188ec8> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
        - locked <0x0000000717188ec8> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

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

"VM Thread" os_prio=2 tid=0x0000000025be9000 nid=0xaa90 runnable

"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x0000000002d0a000 nid=0x3fc0 runnable

"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x0000000002d0b800 nid=0x9cf8 runnable

"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x0000000002d0d000 nid=0x51c runnable

"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x0000000002d0e800 nid=0x24d0 runnable

"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x0000000002d12000 nid=0x618c runnable

"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x0000000002d13000 nid=0x5550 runnable

"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x0000000002d16000 nid=0x8994 runnable

"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x0000000002d17800 nid=0x39cc runnable

"VM Periodic Task Thread" os_prio=2 tid=0x0000000027dd9800 nid=0x5294 waiting on condition

JNI global references: 33


Found one Java-level deadlock:
=============================
"thread2":
  waiting to lock monitor 0x0000000028846468 (object 0x00000007173d4178, a com.jvm.visualvm.Demo4$User),
  which is held by "thread1"
"thread1":
  waiting to lock monitor 0x0000000025bf0bb8 (object 0x00000007173d41b8, a com.jvm.visualvm.Demo4$User),
  which is held by "thread2"

Java stack information for the threads listed above:
===================================================
"thread2":
        at com.jvm.visualvm.Demo4$SynAddRunalbe.run(Demo4.java:49)
        - waiting to lock <0x00000007173d4178> (a com.jvm.visualvm.Demo4$User)
        - locked <0x00000007173d41b8> (a com.jvm.visualvm.Demo4$User)
        at java.lang.Thread.run(Thread.java:745)
"thread1":
        at com.jvm.visualvm.Demo4$SynAddRunalbe.run(Demo4.java:42)
        - waiting to lock <0x00000007173d41b8> (a com.jvm.visualvm.Demo4$User)
        - locked <0x00000007173d4178> (a com.jvm.visualvm.Demo4$User)
        at java.lang.Thread.run(Thread.java:745)

Found 1 deadlock.
從上面的堆棧信息中咱們能夠發現這個內容：「Found one Java-level deadlock」，表示程序中發現了一個死鎖，後面包含跟多詳細的信息，重點下面：

Java stack information for the threads listed above:
===================================================
"thread2":
        at com.jvm.visualvm.Demo4$SynAddRunalbe.run(Demo4.java:49)
        - waiting to lock <0x00000007173d4178> (a com.jvm.visualvm.Demo4$User)
        - locked <0x00000007173d41b8> (a com.jvm.visualvm.Demo4$User)
        at java.lang.Thread.run(Thread.java:745)
"thread1":
        at com.jvm.visualvm.Demo4$SynAddRunalbe.run(Demo4.java:42)
        - waiting to lock <0x00000007173d41b8> (a com.jvm.visualvm.Demo4$User)
        - locked <0x00000007173d4178> (a com.jvm.visualvm.Demo4$User)
        at java.lang.Thread.run(Thread.java:745)

能夠死鎖的代碼是在Demo4.java的49行和42行，此時咱們就能夠去優化代碼，解決死鎖問題。ide

經過jdk提供的工具jconsole排查死鎖問題

jconsole：jdk提供的一個可視化的工具，方便排查程序的一些問題，如：程序內存溢出、死鎖問題等等。更詳細的用法見文檔最後。工具

jconsole位於jdk的bin目錄中性能

步驟一：打開jconsole.exe

能夠看到咱們的程序，點擊鏈接。優化

步驟二：在jconsole窗口中查看線程堆棧信息

步驟三：堆棧中查看到死鎖信息

點擊「檢測死鎖」，能夠看到程序死鎖信息。this

上圖中能夠看到詳細的死鎖信息，和jstack中信息相似。

經過jdk提供的工具VisualVM排查死鎖問題

VisualVM：jdk提供的一個很是強大的排查java程序問題的一個工具，能夠監控程序的性能、查看jvm配置信息、堆快照、線程堆棧信息。算是程序優化的必備工具。

工具位於jdk的bin目錄中。

步驟一：打開VisualVM.exe

步驟二：在visualvm中查看咱們的目標程序

目標程序在visualvm左側窗口中，雙擊便可打開。

步驟三：切換到「線程」窗口

步驟四：查看堆棧信息

在線程窗口中點擊「線程Dump」按鈕

能夠看到產生了一個線程堆棧快照

線程堆棧快照的信息和jstack查看到的信息同樣，便可發現死鎖代碼。

總結

程序中介紹了3中排查死鎖的方法，使用到的都是jdk提供給咱們的工具，這些工具對於咱們優化程序來講，是很是好的，咱們必定要掌握。

相關文章
相關標籤/搜索
每日一句
    每一个你不满意的现在，都有一个你没有努力的曾经。
本站公眾號
   歡迎關注本站公眾號,獲取更多信息
聯繫我們 最近搜索 最新文章 沪ICP备13005482号-10 MyBatis教程 SQL 教程 MySQL教程 Java 教程 Thymeleaf 教程 Hibernate教程 Spring教程 Redis教程