JUC之死锁

@[TOC] (死锁编码及定位分析)

1 概念

死锁是指两个或多个以上的进程在执行过程中,因争夺资源而造成一种互相等待的现象,若无外力干涉那他们都将无法推进下去。如果资源充足,进程的资源请求都能够得到满足,死锁出现的可能性就很低,否则就会因争夺有限的资源而陷入死锁。
在这里插入图片描述

2 产生死锁的原因

  • 系统资源不足
  • 进程运行推进的顺序不对
  • 资源分配不当

死锁产生的四个必要条件:

  • 互斥
    • 解决方法:把互斥的共享资源封装成可同时访问
  • 占有且等待
    • 解决方法:进程请求资源时,要求它不占有任何其它资源,也就是它必须一次性申请到所有的资源,这种方式会导致资源效率低。
  • 非抢占式
    • 解决方法:如果进程不能立即分配资源,要求它不占有任何其他资源,也就是只能够同时获得所有需要资源时,才执行分配操作
  • 循环等待
    • 解决方法:对资源进行排序,要求进程按顺序请求资源。

3 模拟死锁代码

代码:

/**
 * 资源类
 */
class HoldLockThread implements Runnable {
    private String lockA;
    private String lockB;

    // 持有自己的锁,还想得到被人的锁
    public HoldLockThread(String lockA, String lockB) {
        this.lockA = lockA;
        this.lockB = lockB;
    }

    @Override
    public void run() {
        synchronized (lockA) {
            System.out.println(Thread.currentThread().getName() + "\t 自己持有:" + lockA + "\t 尝试获取:" + lockB);

            try {
                TimeUnit.SECONDS.sleep(2);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }

            synchronized (lockB) {
                System.out.println(Thread.currentThread().getName() + "\t 自己持有" + lockB + "\t 尝试获取:" + lockA);
            }
        }
    }


}

public class DeadLockDemo01 {
    public static void main(String[] args) {
        String lockA = "lockA";
        String lockB = "lockB";

        new Thread(new HoldLockThread(lockA, lockB), "t1").start();

        new Thread(new HoldLockThread(lockB, lockA), "t2").start();
    }
}

输出结果:
在这里插入图片描述
可见main线程无法结束。

4.排查死锁

当我们出现死锁的时候,首先需要使用jps命令查看运行的程序:

jps -l

我们能看到DeadLockDemo这个类,一直在运行:
在这里插入图片描述在使用jstack查看堆栈信息:

jstack  8968   # 后面参数是 jps输出的该类的pid

得到的结果:

2020-12-28 17:48:37
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.131-b11 mixed mode):

"DestroyJavaVM" #14 prio=5 os_prio=0 tid=0x00000000038d2800 nid=0x2794 waiting on condition [0x0000000000
000000]
   java.lang.Thread.State: RUNNABLE

"t2" #13 prio=5 os_prio=0 tid=0x000000001ea17000 nid=0x65a4 waiting for monitor entry [0x000000002064f000
]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at Java面试周阳.死锁.HoldLockThread.run(DeadLockDemo01.java:30)
        - waiting to lock <0x000000076e199300> (a java.lang.String)
        - locked <0x000000076e199338> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)

"t1" #12 prio=5 os_prio=0 tid=0x000000001ea16800 nid=0x66b8 waiting for monitor entry [0x000000002054f000
]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at Java面试周阳.死锁.HoldLockThread.run(DeadLockDemo01.java:30)
        - waiting to lock <0x000000076e199338> (a java.lang.String)
        - locked <0x000000076e199300> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)

"Service Thread" #11 daemon prio=9 os_prio=0 tid=0x000000001e971000 nid=0x5abc runnable [0x00000000000000
00]
   java.lang.Thread.State: RUNNABLE

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

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

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

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

"Monitor Ctrl-Break" #6 daemon prio=5 os_prio=0 tid=0x000000001e8a8800 nid=0x6b88 runnable [0x000000001fe
4e000]
   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 <0x000000076e2ba920> (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 <0x000000076e2ba920> (a java.io.InputStreamReader)
        at java.io.BufferedReader.readLine(BufferedReader.java:389)
        at com.intellij.rt.execution.application.AppMainV2$1.run(AppMainV2.java:47)

"Attach Listener" #5 daemon prio=5 os_prio=2 tid=0x000000001e80a800 nid=0x6688 waiting on condition [0x00
00000000000000]
   java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" #4 daemon prio=9 os_prio=2 tid=0x000000001e809000 nid=0x6144 runnable [0x000000000000
0000]
   java.lang.Thread.State: RUNNABLE

"Finalizer" #3 daemon prio=8 os_prio=1 tid=0x000000001e7f3800 nid=0xe9c in Object.wait() [0x000000001fb4f
000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x000000076e008ec8> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
        - locked <0x000000076e008ec8> (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=0x000000001d10d800 nid=0x311c in Object.wait() [0x000
000001fa4f000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x000000076e006b68> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:502)
        at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
        - locked <0x000000076e006b68> (a java.lang.ref.Reference$Lock)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

"VM Thread" os_prio=2 tid=0x000000001d106800 nid=0x6ab0 runnable

"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00000000038e7800 nid=0x63dc runnable

"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00000000038e9800 nid=0x5690 runnable

"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x00000000038eb000 nid=0x5b54 runnable

"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00000000038ec800 nid=0x5b48 runnable

"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x00000000038ef800 nid=0x66c4 runnable

"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x00000000038f0800 nid=0x6744 runnable

"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00000000038f4000 nid=0x5d4c runnable

"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00000000038f5000 nid=0x2194 runnable

"GC task thread#8 (ParallelGC)" os_prio=0 tid=0x00000000038f6000 nid=0x59d0 runnable

"GC task thread#9 (ParallelGC)" os_prio=0 tid=0x00000000038f7800 nid=0x645c runnable

"VM Periodic Task Thread" os_prio=2 tid=0x000000001e977000 nid=0x511c waiting on condition

JNI global references: 16


Found one Java-level deadlock:
=============================
"t2":
  waiting to lock monitor 0x000000001d110d68 (object 0x000000076e199300, a java.lang.String),
  which is held by "t1"
"t1":
  waiting to lock monitor 0x000000001d1133e8 (object 0x000000076e199338, a java.lang.String),
  which is held by "t2"

Java stack information for the threads listed above:
===================================================
"t2":
        at Java面试周阳.死锁.HoldLockThread.run(DeadLockDemo01.java:30)
        - waiting to lock <0x000000076e199300> (a java.lang.String)
        - locked <0x000000076e199338> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)
"t1":
        at Java面试周阳.死锁.HoldLockThread.run(DeadLockDemo01.java:30)
        - waiting to lock <0x000000076e199338> (a java.lang.String)
        - locked <0x000000076e199300> (a java.lang.String)
        at java.lang.Thread.run(Thread.java:748)

Found 1 deadlock.

通过查看最后一行,我们看到 Found 1 deadlock,即存在一个死锁

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值