实战:死锁问题

通过jstack分析死锁情况

1、首先写一个死锁的程序,来造成死锁

public class TestDeadLock{

    private static Object obj1 = new Object();
    private static Object obj2 = new Object();

    public static void main(String[] args) {
        new Thread(new Thread1()).start();
        new Thread(new Thread2()).start();
    }

    private static class Thread1 implements Runnable {

        @Override
        public void run() {
           synchronized (obj1) {
               System.out.println("Thread1 拿到了 obj1 的锁");
               try {
                   Thread.sleep(2000);
               } catch (Exception e) {
                   e.printStackTrace();
               }
               synchronized (obj2) {
                   System.out.println("Thread2 拿到了 obj2 的锁");
               }
           }
        }
    }

    private static class Thread2 implements Runnable {

        @Override
        public void run() {
            synchronized (obj2) {
                System.out.println("Thread1 拿到了 obj2 的锁");
                try {
                    Thread.sleep(2000);
                } catch (Exception e) {
                    e.printStackTrace();
                }
                synchronized (obj1) {
                    System.out.println("Thread2 拿到了 obj1 的锁");
                }
            }
        }
    }
}

2、jstack查看当前JVM的线程运行情况

运行上面程序,出现死锁情况,

[root@node01 jvm_demo02]# java TestDeadLock
Thread1 拿到了 obj1 的锁
Thread1 拿到了 obj2 的锁

然后,连接另一个终端,查看当前运行线程的id为8249,接着通过jstack查看

[root@node01 ~]# jps
8249 TestDeadLock
8271 Jps
[root@node01 ~]# jstack 8249
2019-07-31 11:38:38
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.221-b11 mixed mode):

"Attach Listener" #11 daemon prio=9 os_prio=0 tid=0x00007ff594001000 nid=0x2071 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"DestroyJavaVM" #10 prio=5 os_prio=0 tid=0x00007ff5bc009800 nid=0x203a waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Thread-1" #9 prio=5 os_prio=0 tid=0x00007ff5bc0cc000 nid=0x2044 waiting for monitor entry [0x00007ff5ac6f5000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at TestDeadLock$Thread2.run(TestDeadLock.java:41)
	- waiting to lock <0x00000000e345d7c0> (a java.lang.Object)
	- locked <0x00000000e345d7d0> (a java.lang.Object)
	at java.lang.Thread.run(Thread.java:748)

"Thread-0" #8 prio=5 os_prio=0 tid=0x00007ff5bc0ca000 nid=0x2043 waiting for monitor entry [0x00007ff5ac7f6000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at TestDeadLock$Thread1.run(TestDeadLock.java:23)
	- waiting to lock <0x00000000e345d7d0> (a java.lang.Object)
	- locked <0x00000000e345d7c0> (a java.lang.Object)
	at java.lang.Thread.run(Thread.java:748)

"Service Thread" #7 daemon prio=9 os_prio=0 tid=0x00007ff5bc0b4000 nid=0x2041 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C1 CompilerThread1" #6 daemon prio=9 os_prio=0 tid=0x00007ff5bc0b1000 nid=0x2040 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x00007ff5bc0af000 nid=0x203f waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

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

"Finalizer" #3 daemon prio=8 os_prio=0 tid=0x00007ff5bc07c800 nid=0x203d in Object.wait() [0x00007ff5acdfc000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000e3408ed8> (a java.lang.ref.ReferenceQueue$Lock)
	at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
	- locked <0x00000000e3408ed8> (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=0 tid=0x00007ff5bc077800 nid=0x203c in Object.wait() [0x00007ff5acefd000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x00000000e3406c00> (a java.lang.ref.Reference$Lock)
	at java.lang.Object.wait(Object.java:502)
	at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
	- locked <0x00000000e3406c00> (a java.lang.ref.Reference$Lock)
	at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

"VM Thread" os_prio=0 tid=0x00007ff5bc06e000 nid=0x203b runnable 

"VM Periodic Task Thread" os_prio=0 tid=0x00007ff5bc0b7000 nid=0x2042 waiting on condition 

JNI global references: 5


Found one Java-level deadlock:
=============================
"Thread-1":
  waiting to lock monitor 0x00007ff5a00062c8 (object 0x00000000e345d7c0, a java.lang.Object),
  which is held by "Thread-0"
"Thread-0":
  waiting to lock monitor 0x00007ff5a0004e28 (object 0x00000000e345d7d0, a java.lang.Object),
  which is held by "Thread-1"

Java stack information for the threads listed above:
===================================================
"Thread-1":
	at TestDeadLock$Thread2.run(TestDeadLock.java:41)
	- waiting to lock <0x00000000e345d7c0> (a java.lang.Object)
	- locked <0x00000000e345d7d0> (a java.lang.Object)
	at java.lang.Thread.run(Thread.java:748)
"Thread-0":
	at TestDeadLock$Thread1.run(TestDeadLock.java:23)
	- waiting to lock <0x00000000e345d7d0> (a java.lang.Object)
	- locked <0x00000000e345d7c0> (a java.lang.Object)
	at java.lang.Thread.run(Thread.java:748)

Found 1 deadlock.

[root@node01 ~]# 
通过上面打印出的内存可以看到,当前发生了一个Java-level级的死锁,Thread-1已经获取了<0x00000000e345d7d0>的锁,等待获取<0x00000000e345d7c0>的锁,而Thread-0已经获取了<0x00000000e345d7c0>的锁,等待获取<0x00000000e345d7d0>的锁
  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值