Jstack工具检测死锁

最新推荐文章于 2024-05-20 11:49:02 发布
最新推荐文章于 2024-05-20 11:49:02 发布
阅读量610 收藏 1
点赞数
分类专栏： Java高级-虚拟机 文章标签： java
原文链接：https://www.jianshu.com/p/8d5782bc596e
版权

文章目录

构建死锁代码


import java.util.concurrent.TimeUnit;
import java.util.concurrent.locks.Lock;
import java.util.concurrent.locks.ReentrantLock;

public class DeathLock {

    private static Lock lock1 = new ReentrantLock();
    private static Lock lock2 = new ReentrantLock();

    public static void deathLock() {
        Thread t1 = new Thread() {
            @Override
            public void run() {
                try {
                    lock1.lock();
                    TimeUnit.SECONDS.sleep(1);
                    lock2.lock();
                } catch (InterruptedException e) {
                    e.printStackTrace();
                }
            }
        };
        Thread t2 = new Thread() {
            @Override
            public void run() {
                try {
                    lock2.lock();
                    TimeUnit.SECONDS.sleep(1);
                    lock1.lock();
                } catch (InterruptedException e) {
                    e.printStackTrace();
                }
            }
        };

        t1.setName("mythread1");
        t2.setName("mythread2");
        t1.start();
        t2.start();
    }

    public static void main(String[] args) {
        deathLock();
    }
}

使用jstack命令查看线程死锁

C:\Users\admin>jstack 23388
2020-05-12 14:05:36
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.181-b13 mixed mode):

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

"mythread2" #13 prio=5 os_prio=0 tid=0x000000001e07e000 nid=0x2f44 waiting on condition [0x00000000203cf000]
   java.lang.Thread.State: WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x000000076b7c7ee8> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
        at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
        at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
        at thread.DeathLock$2.run(DeathLock.java:31)

"mythread1" #12 prio=5 os_prio=0 tid=0x000000001e07d000 nid=0x4e24 waiting on condition [0x00000000202cf000]
   java.lang.Thread.State: WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x000000076b7c7f18> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
        at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
        at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
        at thread.DeathLock$1.run(DeathLock.java:19)

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

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

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

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

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

"Monitor Ctrl-Break" #6 daemon prio=5 os_prio=0 tid=0x000000001df50800 nid=0x26f4 runnable [0x000000001f3ce000]
   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 <0x000000076b84a018> (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 <0x000000076b84a018> (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=0x000000001dd06000 nid=0x1448 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

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

"Finalizer" #3 daemon prio=8 os_prio=1 tid=0x000000001dce3000 nid=0x42e8 in Object.wait() [0x000000001f06f000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x000000076b588ed0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
        - locked <0x000000076b588ed0> (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=0x000000001c5fc800 nid=0x4154 in Object.wait() [0x000000001ef6f000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x000000076b586bf8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:502)
        at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
        - locked <0x000000076b586bf8> (a java.lang.ref.Reference$Lock)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

"VM Thread" os_prio=2 tid=0x000000001dcc2800 nid=0x4720 runnable

"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00000000028dc000 nid=0xa34 runnable

"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00000000028dd800 nid=0x4e34 runnable

"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x00000000028df000 nid=0x4c48 runnable

"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00000000028e1800 nid=0x48d0 runnable

"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x00000000028e3800 nid=0xa40 runnable

"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x00000000028e5000 nid=0x4a14 runnable

"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00000000028e8000 nid=0x2b60 runnable

"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00000000028e9000 nid=0x3514 runnable

"GC task thread#8 (ParallelGC)" os_prio=0 tid=0x00000000028ea800 nid=0x58f4 runnable

"GC task thread#9 (ParallelGC)" os_prio=0 tid=0x00000000028eb800 nid=0x3644 runnable

"VM Periodic Task Thread" os_prio=2 tid=0x000000001e052000 nid=0x4480 waiting on condition

JNI global references: 12


Found one Java-level deadlock:
=============================
"mythread2":
  waiting for ownable synchronizer 0x000000076b7c7ee8, (a java.util.concurrent.locks.ReentrantLock$NonfairSync),
  which is held by "mythread1"
"mythread1":
  waiting for ownable synchronizer 0x000000076b7c7f18, (a java.util.concurrent.locks.ReentrantLock$NonfairSync),
  which is held by "mythread2"

Java stack information for the threads listed above:
===================================================
"mythread2":
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x000000076b7c7ee8> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
        at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
        at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
        at thread.DeathLock$2.run(DeathLock.java:31)
"mythread1":
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x000000076b7c7f18> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
        at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
        at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
        at thread.DeathLock$1.run(DeathLock.java:19)

Found 1 deadlock.

Jstack用法

Jstack查看线程状态

C:\Users\admin>jstack -help
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

jstack统计线程数

jstack -l 28367 | grep 'java.lang.Thread.State' | wc -l

jstack检测cpu高

在这里插入图片描述
步骤一：查看cpu占用高进程

top

Mem:  16333644k total,  9472968k used,  6860676k free,   165616k buffers
Swap:        0k total,        0k used,        0k free,  6665292k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND     
17850 root      20   0 7588m 112m  11m S 100.7  0.7  47:53.80 java       
 1552 root      20   0  121m  13m 8524 S  0.7  0.1  14:37.75 AliYunDun   
 3581 root      20   0 9750m 2.0g  13m S  0.7 12.9 298:30.20 java        
    1 root      20   0 19360 1612 1308 S  0.0  0.0   0:00.81 init        
    2 root      20   0     0    0    0 S  0.0  0.0   0:00.00 kthreadd    
    3 root      RT   0     0    0    0 S  0.0  0.0   0:00.14 migration/0

步骤二：查看cpu占用高线程

top -H -p 17850

top - 17:43:15 up 5 days,  7:31,  1 user,  load average: 0.99, 0.97, 0.91
Tasks:  32 total,   1 running,  31 sleeping,   0 stopped,   0 zombie
Cpu(s):  3.7%us,  8.9%sy,  0.0%ni, 87.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:  16333644k total,  9592504k used,  6741140k free,   165700k buffers
Swap:        0k total,        0k used,        0k free,  6781620k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
17880 root      20   0 7588m 112m  11m R 99.9  0.7  50:47.43 java
17856 root      20   0 7588m 112m  11m S  0.3  0.7   0:02.08 java
17850 root      20   0 7588m 112m  11m S  0.0  0.7   0:00.00 java
17851 root      20   0 7588m 112m  11m S  0.0  0.7   0:00.23 java
17852 root      20   0 7588m 112m  11m S  0.0  0.7   0:02.09 java
17853 root      20   0 7588m 112m  11m S  0.0  0.7   0:02.12 java
17854 root      20   0 7588m 112m  11m S  0.0  0.7   0:02.07 java

步骤三：转换线程ID

printf "%x\n" 17880          
45d8

步骤四：定位cpu占用线程

jstack 17850|grep 45d8 -A 30
"pool-1-thread-11" #20 prio=5 os_prio=0 tid=0x00007fc860352800 nid=0x45d8 runnable [0x00007fc8417d2000]
   java.lang.Thread.State: RUNNABLE
        at java.io.FileOutputStream.writeBytes(Native Method)
        at java.io.FileOutputStream.write(FileOutputStream.java:326)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        - locked <0x00000006c6c2e708> (a java.io.BufferedOutputStream)
        at java.io.PrintStream.write(PrintStream.java:482)
        - locked <0x00000006c6c10178> (a java.io.PrintStream)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
        at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
        - locked <0x00000006c6c26620> (a java.io.OutputStreamWriter)
        at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
        at java.io.PrintStream.write(PrintStream.java:527)
        - eliminated <0x00000006c6c10178> (a java.io.PrintStream)
        at java.io.PrintStream.print(PrintStream.java:597)
        at java.io.PrintStream.println(PrintStream.java:736)
        - locked <0x00000006c6c10178> (a java.io.PrintStream)
        at com.demo.guava.HardTask.call(HardTask.java:18)
        at com.demo.guava.HardTask.call(HardTask.java:9)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

"pool-1-thread-10" #19 prio=5 os_prio=0 tid=0x00007fc860345000 nid=0x45d7 waiting on condition [0x00007fc8418d3000]
   java.lang.Thread.State: WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x00000006c6c14178> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

参考文章：
jstack命令解析https://www.jianshu.com/p/8d5782bc596e

m0_46485771
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
检测死锁的几个工具：JStack、JConsole、JVisualVM、ThreadMXBean
d303577562的博客
10-27 1099
如何监测死锁
jstack排查死锁问题
个人日常记录,分析
10-24 2086
死锁问题排查学习,一起进步
JVM优化之使用Jstack命令查找JVM死锁
最新发布
qq_41139119的博客
05-20 226
JVM优化之使用Jstack命令查找JVM死锁
死锁检测的常用3种方法
qq_38860250的博客
01-18 5862
死锁（Dead Lock）是指两个或两个以上的进程在执行过程中，由于竞争资源或者由于彼此通信而造成的一种阻塞的现象，若无外力作用，它们都将无法推进下去。此时称系统处于死锁状态或系统产生了死锁，这些永远在互相等待的进程称为死锁进程。
java jstack 死锁_用jstack找死锁
weixin_39620001的博客
02-16 225
java死锁主要依靠jstack命令来查找。检测jstack先配置好jdk环境变量，打开一个终端命令行，输入jstack回车。如果看到如下的字样，说明jstack是可用的。Usage:jstack [-l][-e] (to connect to running process)Options:-l long listing. Prints additional information about...
JVM之jstack实战死锁问题
write less , do more
10-10 1597
这个条件占用部分资源的线程进一步申请其他资源时，如果申请不到可以主动释放它占有的资源，这样不可抢占这个条件就破坏掉了。线程尝试获取锁的时候加上一定的时限，超过时限则放弃对该锁的请求，并释放自己占有的锁。编写代码，启动2个线程，Thread1拿到了obj1锁，准备去拿obj2锁时，obj2已经被Thread2锁定，所以发送了死锁。，即存在一个等待队列：T1等待占有T2的资源，T2等待占有T3的资源，T3等待占有T1的资源。这样就形成了一个等待环路。，即当资源请求者在请求其他的资源的同时保持对原有资源的占有。
使用jstack排查JVM进程死锁
水妖
10-28 1577
jstack查看运行期间线程信息神器
操作系统死锁检测与解除
10-27
为了检测死锁，Java提供了一个内置的诊断工具——`jstack`，它可以帮助开发者查看线程堆栈信息，找出可能存在的死锁状态。通过分析`jstack`输出，我们可以找到那些处于"等待持有锁"状态的线程，如果发现有循环等待的...
如何通过jstack命令dump线程信息
10-15
这种情况下，`jstack`的输出会包含一个死锁检测段，指出哪些线程在哪个类的哪一行代码上发生了死锁。 在示例代码中，`DeadLockDemo`类的`deadLock()`方法创建了两个线程`t1`和`t2`。线程`t1`先获取锁A，然后尝试...
java线程分析工具TDA
06-21
当应用程序出现性能问题或疑似死锁时，开发者通常会使用`jstack`命令来生成线程堆栈，这是一个内置在JDK中的命令行工具。 TDA的使用流程如下： 1. **生成线程堆栈**：首先，你需要通过`jstack`命令对目标Java进程...
Java线程检测和数据收集工具
11-03
本文将深入探讨如何使用Java提供的工具——`jps`和`jstack`，以及如何通过Shell脚本来定时收集Java进程的线程信息。 首先，`jps`（JVM Process Status）是Java虚拟机进程状况工具，它能够列出正在运行的Java进程ID...
什么是死锁，如何避免死锁？Java死锁详解
12-20
Java中检测死锁的方法： Java提供了一些工具来检测和解决死锁问题。例如，可以使用JDK的`jstack`命令或者IDE如IntelliJ IDEA的调试工具来查看线程堆栈信息，找出哪个线程被阻塞并分析其状态。在上述例子中，如果两个...
使用jstack 发现死锁
jueshengtianya的专栏
03-06 983
参考：http://blog.chinaunix.net/uid-20104447-id-4075333.html 1. 据java的sdk说明，当调用一个线程的stop时（暂时不管该不该使用该方法），线程会立即退出，但是下面的却没有，是什么原因呢？ package java_jni; public class Main { public static void main(Stri
使用Jstack、JConsole和jvisualvm进行死锁分析
fen_fen的专栏
07-27 784
使用Jstack、Jconsole和jvisualvm进行死锁分析
jstack命令解析
lixiangchibang的博客
04-25 654
jstack用法 /opt/java8/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> .
使用 jstack或者jconsole查看死锁状态
wppwpp1的专栏
06-24 467
1,有时候运行程序时会出现代码死锁，可以通过jstack进行查看， 1.1 死锁代码如下： import lombok.extern.slf4j.Slf4j; import static cn.itcast.n2.util.Sleeper.sleep; @Slf4j(topic = "c.TestDeadLock") public class TestDeadLock { public static void main(String[] args) { test1();.
【JVM】Jstack实战死循环与死锁
好学若饥，谦卑若愚
08-18 2445
死锁检测 # 查看Java PID（进程号） [root@localhost ~]# jps -l # 控制台输出线程的dump信息 [root@localhost tomcat]# jstack PID [root@localhost tomcat]# jstack Usage: jstack [-l] &amp;lt;pid&amp;gt; (to connect to ...
用jstack分析解决进程死锁问题
L-BAKE
04-23 789
【转自：http://blog.sina.com.cn/s/blog_855eab95010157uv.html】
jstack分析死锁
huchunlinnk的专栏
01-15 2164
先附上死锁代码：package test; public class lock {     public static Object lock1=new Object();     public static Object lock2=new Object();     public static void main(String[] args) {         new Thre
检测java死锁的工具有哪些
06-09
2. jstack：是JDK自带的一款命令行工具，可以用于打印Java进程的线程堆栈信息，也可以检测死锁。 3. VisualVM：是一个功能强大的Java虚拟机监视和分析工具，可以用于监视JVM的性能、内存使用情况、线程状态等信息，...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值