Java自带的性能监测工具之jstack

最新推荐文章于 2022-07-19 08:57:17 发布
最新推荐文章于 2022-07-19 08:57:17 发布
阅读量271 收藏
点赞数
文章标签： java 大数据 开发工具
原文链接：https://my.oschina.net/wangmengjun/blog/865125
版权

2019独角兽企业重金招聘Python工程师标准>>> hot3.png

本文继续介绍Java自带的性能监测工具，本文使用jstack (Java Stack Trace)工具来玩~

使用jstack命令工具可以得到线程堆栈信息，根据这些线程堆栈信息，我们可以去检查Java程序出现的问题，如检测死锁，并输出死锁的信息~的排查。

在使用jstack命令之前，可以先使用jstack -h来查看jstack命令相关的使用方法，包括有哪些参数等~

[root@dev18 ~]# jstack -h
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 [option] <pid>

使用jstack -m <pid>打印java和native frames 的信息，如jstack -m 12905，这里的12905是Zookeeper服务的进程ID~

[root@dev18 ~]# jstack -m 12905
Attaching to process ID 12905, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 24.71-b01
Deadlock Detection:

No deadlocks found.

----------------- 12908 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad07875a5	Unsafe_Park + 0x125
0x00007fcacc4b17f8	* sun.misc.Unsafe.park(boolean, long) bci:0 (Interpreted frame)
0x00007fcacc4a5058	* java.util.concurrent.locks.LockSupport.park(java.lang.Object) bci:14 line:186 (Interpreted frame)
0x00007fcacc4a5058	* java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt() bci:1 line:834 (Interpreted frame)
0x00007fcacc4a5350	* java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(int) bci:72 line:994 (Interpreted frame)
0x00007fcacc4a5058	* java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(int) bci:24 line:1303 (Interpreted frame)
0x00007fcacc4a5058	* java.util.concurrent.CountDownLatch.await() bci:5 line:236 (Interpreted frame)
0x00007fcacc4a5058	* org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(org.apache.zookeeper.server.ServerConfig) bci:134 line:122 (Interpreted frame)
0x00007fcacc4a5058	* org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(java.lang.String[]) bci:49 line:87 (Interpreted frame)
0x00007fcacc4a5058	* org.apache.zookeeper.server.ZooKeeperServerMain.main(java.lang.String[]) bci:10 line:53 (Interpreted frame)
0x00007fcacc4a5058	* org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(java.lang.String[]) bci:84 line:116 (Interpreted frame)
0x00007fcacc4a5058	* org.apache.zookeeper.server.quorum.QuorumPeerMain.main(java.lang.String[]) bci:10 line:78 (Interpreted frame)
0x00007fcacc49f4e7	<StubRoutines>
0x00007fcad040a085	_ZN9JavaCalls11call_helperEP9JavaValueP12methodHandleP17JavaCallArgumentsP6Thread + 0x365
0x00007fcad0408ae8	_ZN9JavaCalls4callEP9JavaValue12methodHandleP17JavaCallArgumentsP6Thread + 0x28
0x00007fcad0442a99	_ZL17jni_invoke_staticP7JNIEnv_P9JavaValueP8_jobject11JNICallTypeP10_jmethodIDP18JNI_ArgumentPusherP6Thread + 0x219
0x00007fcad044b6b2	jni_CallStaticVoidMethod + 0x162
0x00007fcad0c866d9	JavaMain + 0x7e9
----------------- 12909 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad05eb5cf	_ZN7Monitor5IWaitEP6Threadl + 0xef
0x00007fcad05ebd5e	_ZN7Monitor4waitEblb + 0x22e
0x00007fcad035fcc3	_ZN13GCTaskManager8get_taskEj + 0x43
0x00007fcad0361388	_ZN12GCTaskThread3runEv + 0x188
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12910 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad05eb5cf	_ZN7Monitor5IWaitEP6Threadl + 0xef
0x00007fcad05ebd5e	_ZN7Monitor4waitEblb + 0x22e
0x00007fcad035fcc3	_ZN13GCTaskManager8get_taskEj + 0x43
0x00007fcad0361388	_ZN12GCTaskThread3runEv + 0x188
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12911 -----------------
0x000000358d40ba0e	__pthread_cond_timedwait + 0x13e
0x00007fcad05eb87e	_ZN7Monitor5IWaitEP6Threadl + 0x39e
0x00007fcad05ebd5e	_ZN7Monitor4waitEblb + 0x22e
0x00007fcad07b1ff9	_ZN8VMThread4loopEv + 0x339
0x00007fcad07b2300	_ZN8VMThread3runEv + 0x70
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12912 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad061860d	_ZN13ObjectMonitor4waitElbP6Thread + 0x9bd
0x00007fcad0487578	JVM_MonitorWait + 0x168
0x00007fcacc52dec8	<Unknown compiled code>
0x00007fcacc4a5058	* java.lang.Object.wait() bci:2 line:503 (Interpreted frame)
0x00007fcacc4a5058	* java.lang.ref.Reference$ReferenceHandler.run() bci:46 line:133 (Interpreted frame)
0x00007fcacc49f4e7	<StubRoutines>
0x00007fcad040a085	_ZN9JavaCalls11call_helperEP9JavaValueP12methodHandleP17JavaCallArgumentsP6Thread + 0x365
0x00007fcad0408ae8	_ZN9JavaCalls4callEP9JavaValue12methodHandleP17JavaCallArgumentsP6Thread + 0x28
0x00007fcad0408db7	_ZN9JavaCalls12call_virtualEP9JavaValue11KlassHandleP6SymbolS4_P17JavaCallArgumentsP6Thread + 0x197
0x00007fcad0408ed7	_ZN9JavaCalls12call_virtualEP9JavaValue6Handle11KlassHandleP6SymbolS5_P6Thread + 0x47
0x00007fcad0485ef5	_ZL12thread_entryP10JavaThreadP6Thread + 0xe5
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12913 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad061860d	_ZN13ObjectMonitor4waitElbP6Thread + 0x9bd
0x00007fcad0487578	JVM_MonitorWait + 0x168
0x00007fcacc52dec8	<Unknown compiled code>
0x00007fcacc4a5058	* java.lang.ref.ReferenceQueue.remove(long) bci:44 line:135 (Interpreted frame)
0x00007fcacc4a5233	* java.lang.ref.ReferenceQueue.remove() bci:2 line:151 (Interpreted frame)
0x00007fcacc4a5233	* java.lang.ref.Finalizer$FinalizerThread.run() bci:36 line:209 (Interpreted frame)
0x00007fcacc49f4e7	<StubRoutines>
0x00007fcad040a085	_ZN9JavaCalls11call_helperEP9JavaValueP12methodHandleP17JavaCallArgumentsP6Thread + 0x365
0x00007fcad0408ae8	_ZN9JavaCalls4callEP9JavaValue12methodHandleP17JavaCallArgumentsP6Thread + 0x28
0x00007fcad0408db7	_ZN9JavaCalls12call_virtualEP9JavaValue11KlassHandleP6SymbolS4_P17JavaCallArgumentsP6Thread + 0x197
0x00007fcad0408ed7	_ZN9JavaCalls12call_virtualEP9JavaValue6Handle11KlassHandleP6SymbolS5_P6Thread + 0x47
0x00007fcad0485ef5	_ZL12thread_entryP10JavaThreadP6Thread + 0xe5
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12914 -----------------
0x000000358d40d9b0	sem_wait + 0x30
0x00007fcad0622365	_ZL19signal_thread_entryP10JavaThreadP6Thread + 0x95
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12915 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad05eb5cf	_ZN7Monitor5IWaitEP6Threadl + 0xef
0x00007fcad05ebdd6	_ZN7Monitor4waitEblb + 0x2a6
0x00007fcad0254d88	_ZN12CompileQueue3getEv + 0x128
0x00007fcad0258e8a	_ZN13CompileBroker20compiler_thread_loopEv + 0x13a
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12916 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad05eb5cf	_ZN7Monitor5IWaitEP6Threadl + 0xef
0x00007fcad05ebdd6	_ZN7Monitor4waitEblb + 0x2a6
0x00007fcad0254d88	_ZN12CompileQueue3getEv + 0x128
0x00007fcad0258e8a	_ZN13CompileBroker20compiler_thread_loopEv + 0x13a
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12917 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad05eb5cf	_ZN7Monitor5IWaitEP6Threadl + 0xef
0x00007fcad05ebd5e	_ZN7Monitor4waitEblb + 0x22e
0x00007fcad06b9f27	_ZN13ServiceThread20service_thread_entryEP10JavaThreadP6Thread + 0x197
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12918 -----------------
0x000000358d0df143	__libc_poll + 0x53
0x00007fcac4827037	Java_java_net_PlainSocketImpl_socketAccept + 0x1e7
0x00007fcacc4b17f8	* java.net.PlainSocketImpl.socketAccept(java.net.SocketImpl) bci:0 (Interpreted frame)
0x00007fcacc4a5058	* java.net.AbstractPlainSocketImpl.accept(java.net.SocketImpl) bci:7 line:398 (Interpreted frame)
0x00007fcacc4a5058	* java.net.ServerSocket.implAccept(java.net.Socket) bci:60 line:530 (Interpreted frame)
0x00007fcacc4a5058	* java.net.ServerSocket.accept() bci:48 line:498 (Interpreted frame)
0x00007fcacc4a5233	* sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop() bci:55 line:388 (Interpreted frame)
0x00007fcacc4a5058	* sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run() bci:1 line:360 (Interpreted frame)
0x00007fcacc4a5706	* java.lang.Thread.run() bci:11 line:745 (Interpreted frame)
0x00007fcacc49f4e7	<StubRoutines>
0x00007fcad040a085	_ZN9JavaCalls11call_helperEP9JavaValueP12methodHandleP17JavaCallArgumentsP6Thread + 0x365
0x00007fcad0408ae8	_ZN9JavaCalls4callEP9JavaValue12methodHandleP17JavaCallArgumentsP6Thread + 0x28
0x00007fcad0408db7	_ZN9JavaCalls12call_virtualEP9JavaValue11KlassHandleP6SymbolS4_P17JavaCallArgumentsP6Thread + 0x197
0x00007fcad0408ed7	_ZN9JavaCalls12call_virtualEP9JavaValue6Handle11KlassHandleP6SymbolS5_P6Thread + 0x47
0x00007fcad0485ef5	_ZL12thread_entryP10JavaThreadP6Thread + 0xe5
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12919 -----------------
0x000000358d40ba0e	__pthread_cond_timedwait + 0x13e
0x00007fcad05eb87e	_ZN7Monitor5IWaitEP6Threadl + 0x39e
0x00007fcad05ebd5e	_ZN7Monitor4waitEblb + 0x22e
0x00007fcad075f951	_ZNK13WatcherThread5sleepEv + 0x71
0x00007fcad075fe6e	_ZN13WatcherThread3runEv + 0x5e
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12920 -----------------
0x000000358d0e8f63	__GI_epoll_wait + 0x33
0x00007fcacc5233d2	<Unknown compiled code>
----------------- 12921 -----------------
0x000000358d40ba0e	__pthread_cond_timedwait + 0x13e
0x00007fcad0617eab	_ZN13ObjectMonitor4waitElbP6Thread + 0x25b
0x00007fcad0487578	JVM_MonitorWait + 0x168
0x00007fcacc52dec8	<Unknown compiled code>
----------------- 12922 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad07875a5	Unsafe_Park + 0x125
0x00007fcacc545e4a	<Unknown compiled code>
----------------- 12923 -----------------
0x000000358d40b63c	__pthread_cond_wait + 0xcc
0x00007fcad07875a5	Unsafe_Park + 0x125
0x00007fcacc545e4a	<Unknown compiled code>
----------------- 17907 -----------------
0x000000358d40eadd	__libc_accept + 0x2d
0x00007fcad010972b	_ZN14AttachListener7dequeueEv + 0x7b
0x00007fcad010827a	_ZL28attach_listener_thread_entryP10JavaThreadP6Thread + 0x19a
0x00007fcad076392f	_ZN10JavaThread17thread_main_innerEv + 0xdf
0x00007fcad0763a35	_ZN10JavaThread3runEv + 0xf5
0x00007fcad062a4b8	_ZL10java_startP6Thread + 0x108
----------------- 12905 -----------------
0x000000358d4082ad	pthread_join + 0x10d
[root@dev18 ~]#

 

接下来，我们就来看一下jstack查看死锁的示例~

使用jstack查看死锁

死锁Java代码

public class Deadlock {
    static class Friend {
        private final String name;
        public Friend(String name) {
            this.name = name;
        }
        public String getName() {
            return this.name;
        }
        public synchronized void bow(Friend bower) {
            System.out.format("%s: %s"
                + "  has bowed to me!%n", 
                this.name, bower.getName());
            bower.bowBack(this);
        }
        public synchronized void bowBack(Friend bower) {
            System.out.format("%s: %s"
                + " has bowed back to me!%n",
                this.name, bower.getName());
        }
    }

    public static void main(String[] args) {
        final Friend alphonse =
            new Friend("Alphonse");
        final Friend gaston =
            new Friend("Gaston");
        new Thread(new Runnable() {
            public void run() { alphonse.bow(gaston); }
        }).start();
        new Thread(new Runnable() {
            public void run() { gaston.bow(alphonse); }
        }).start();
    }
}

查看死锁进程

在Eclipse上运行上述Deadlock程序，然后使用jps -l查看死锁进程ID~

C:\Users\wangmengjun>jps -l
5752 sun.tools.jps.Jps
16724 F:\JavaDeveloper\eclipse\\plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
11172 Deadlock
17868

使用jstack检测死锁原因

使用jps -l查看死锁进程ID，我们得知死锁程序的PID为11172~

接下来，我们就使用jstack -l 11172检测死锁原因~

C:\Users\wangmengjun>jstack -l 11172
2017-03-22 19:06:29
Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode):

"DestroyJavaVM" prio=6 tid=0x0000000002a72800 nid=0x3d8c waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Thread-1" prio=6 tid=0x0000000011373000 nid=0x46c4 waiting for monitor entry [0x00000000118df000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at Deadlock$Friend.bowBack(Deadlock.java:19)
        - waiting to lock <0x00000007ab134018> (a Deadlock$Friend)
        at Deadlock$Friend.bow(Deadlock.java:16)
        - locked <0x00000007ab134060> (a Deadlock$Friend)
        at Deadlock$2.run(Deadlock.java:34)
        at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
        - None

"Thread-0" prio=6 tid=0x000000000f9c7800 nid=0x2f94 waiting for monitor entry [0x00000000117df000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at Deadlock$Friend.bowBack(Deadlock.java:19)
        - waiting to lock <0x00000007ab134060> (a Deadlock$Friend)
        at Deadlock$Friend.bow(Deadlock.java:16)
        - locked <0x00000007ab134018> (a Deadlock$Friend)
        at Deadlock$1.run(Deadlock.java:31)
        at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
        - None

"Service Thread" daemon prio=6 tid=0x000000000f987000 nid=0x3480 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"C2 CompilerThread1" daemon prio=10 tid=0x000000000f978000 nid=0x4468 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"C2 CompilerThread0" daemon prio=10 tid=0x000000000f972800 nid=0x4558 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Attach Listener" daemon prio=10 tid=0x000000000f971800 nid=0x4ba4 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Signal Dispatcher" daemon prio=10 tid=0x000000000f96e800 nid=0x4860 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Finalizer" daemon prio=8 tid=0x000000000f921000 nid=0x4964 in Object.wait() [0x0000000010cdf000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000007ab084858> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(Unknown Source)
        - locked <0x00000007ab084858> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(Unknown Source)
        at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)

   Locked ownable synchronizers:
        - None

"Reference Handler" daemon prio=10 tid=0x000000000f917800 nid=0x30bc in Object.wait() [0x0000000010bdf000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000007ab084470> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:503)
        at java.lang.ref.Reference$ReferenceHandler.run(Unknown Source)
        - locked <0x00000007ab084470> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
        - None

"VM Thread" prio=10 tid=0x000000000f912000 nid=0x3330 runnable

"GC task thread#0 (ParallelGC)" prio=6 tid=0x0000000002a88800 nid=0x4870 runnable

"GC task thread#1 (ParallelGC)" prio=6 tid=0x0000000002a8a000 nid=0x4324 runnable

"GC task thread#2 (ParallelGC)" prio=6 tid=0x0000000002a8c000 nid=0x41d4 runnable

"GC task thread#3 (ParallelGC)" prio=6 tid=0x0000000002a8d800 nid=0x26d4 runnable

"VM Periodic Task Thread" prio=10 tid=0x000000000f991000 nid=0x17a4 waiting on condition

JNI global references: 122


Found one Java-level deadlock:
=============================
"Thread-1":
  waiting to lock monitor 0x000000000f91efa8 (object 0x00000007ab134018, a Deadlock$Friend),
  which is held by "Thread-0"
"Thread-0":
  waiting to lock monitor 0x000000000f920398 (object 0x00000007ab134060, a Deadlock$Friend),
  which is held by "Thread-1"

Java stack information for the threads listed above:
===================================================
"Thread-1":
        at Deadlock$Friend.bowBack(Deadlock.java:19)
        - waiting to lock <0x00000007ab134018> (a Deadlock$Friend)
        at Deadlock$Friend.bow(Deadlock.java:16)
        - locked <0x00000007ab134060> (a Deadlock$Friend)
        at Deadlock$2.run(Deadlock.java:34)
        at java.lang.Thread.run(Unknown Source)
"Thread-0":
        at Deadlock$Friend.bowBack(Deadlock.java:19)
        - waiting to lock <0x00000007ab134060> (a Deadlock$Friend)
        at Deadlock$Friend.bow(Deadlock.java:16)
        - locked <0x00000007ab134018> (a Deadlock$Friend)
        at Deadlock$1.run(Deadlock.java:31)
        at java.lang.Thread.run(Unknown Source)

Found 1 deadlock.

从上述输出的信息中可以看出死锁的信息~ 

190909_P2Zv_2911530.png

转载于:https://my.oschina.net/wangmengjun/blog/865125

weixin_34192816
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Jstack-简单使用
Hedyqing的博客
09-08 272
Jstack：主要用来查看某个java进程内的线程堆栈信息 语法格式为：jstack [option] pid：输出当前压测接口的实时堆栈信息 命令行参数： -l long listings:会打印出额外的锁信息，在发送死锁时可以来观察锁持有情况 -m mixed mode：不仅会输出java堆栈信息，还会输出C/C++堆栈信息 jstack可以定位到线程堆栈，根据堆栈信息定位到具体代码，所以在JVM性能调优中使用很多 举个例子；找出java进程中最耗费CPU的java线程并定位堆栈信息 1.先找出部
Java内存监控工具（下）
Dreamer016的博客
07-22 1046
文章目录jstack语法option-F-l-mpid实战1、运行如下代码2、执行jps命令获取进程id:3、执行jstack pid命令：查看pid进程内线程信息：线程与Monitor进入区(Entrt Set)拥有者(The Owner)等待区(Wait Set)线程状态：1、NEW2、RUNNABLE3、BLOCKED4、WAITING5、TIMED_WAITING6、TERMINATED：...
Java排查问题工具
gentlezuo的博客
07-29 627
文章目录jinfo用法例子问题jps用法例子jconsole用法例子jcmd用法例子jstack例子jmap使用例子jhat使用例子jstat使用总结 jdk自带一些工具来查看或更改java程序的信息。在程序出现问题时可以用它们分析。 jinfo jinfo用来查看JVM的参数，更改参数等。 用法 $ jinfo Usage: jinfo [option] <pid> (to connect to running process) jinfo [optio
LHon（学习笔记）——分析OOM产生原因
七生
08-12 522
文章目录JVMOOM堆内存的OOMHeap Dumpjmapjstack JVM 在弄清楚OOM产生的原因之前，我们务必要搞清楚Java的内存模型，也就是JVM，这可以参考我之前的一个学习笔记 JVM学习笔记 先来看一下要用到的JVM的一些参数： 参数名称 含义 -Xms 初始堆大小 -Xmx 最大堆大小 -Xmn 年轻代大小 -Xss 每个线程的堆栈大小 -XX:+HeapDumpOnOutOfMemoryError 目录下生成堆的Dump文件 当初始化堆内存容量
java进程假死_java进程假死
weixin_31550647的博客
02-13 820
进程假死，查看dump信息如下Attaching to process ID 24746, please wait...Debugger attached successfully.Server compiler detected.JVM version is 25.101-b13Deadlock Detection:No deadlocks found.Thread 6886: (state =...
Java多线程程序死锁检查 JCarder
06-02
除了JCarder，Java还提供了其他的死锁检测工具和手段，如JConsole、VisualVM和JDK自带的jstack命令。这些工具都可以帮助我们分析线程状态，找出可能导致死锁的原因。 在编写多线程程序时，预防死锁的一些最佳实践...
jvm分析资料及工具1
最新发布
10-13
本资源包“jvm分析资料及工具1”显然是针对Java开发者，尤其是那些希望深入理解JVM内部工作原理、优化应用程序性能的人员。在这里，我们将深入探讨JVM分析的相关知识点，并介绍一些常用工具。 1. **JVM内存模型**：...
Java高级面试题附答案汇总（2021年Java面试题及答案大全）
07-22
本资源摘要信息涵盖了Java高级面试题附答案汇总（2021年Java面试题及答案大全），涵盖了多个知识点，包括Java高级面试题、序列化、多线程同步、GC算法、集合类型、JDK自带的监控和性能分析工具等。 1. ...
jvm监控工具
04-04
8. **第三方工具**：除了Java自带的工具，还有许多第三方工具如JProfiler、YourKit、Memory Analyzer Tool (MAT)等，它们提供了更高级的功能，如深度内存分析、CPU剖析、性能瓶颈定位等。 9. **GC (Garbage ...
java 监控线程
06-27
1. **JConsole**: JConsole是Java自带的可视化监控工具，它可以显示JVM的各种信息，包括线程的详细状态、CPU使用率等。通过JMX（Java Management Extensions）接口，开发者可以远程监控应用的线程情况。 2. **...
java 运行一段时间_java 应用程序运行一段时间，自己就进行工作了？
weixin_28724661的博客
02-16 217
Debuggerattachedsuccessfully.Servercompilerdetected.JVMversionis25.162-b12DeadlockDetection:Nodeadlocksfound.Thread159221:(state=BLOCKED)-sun.misc.Unsafe.park(boolean,lon...Debugger attached successfu...
jstack 的使用《jvm常用命令》
不积跬步，无以至千里；不积小流，无以成江海。
05-06 912
介绍 jstack用于生成java虚拟机当前时刻的线程快照。线程快照是当前java虚拟机内每一条线程正在执行的方法堆栈的集合，生成线程快照的主要目的是定位线程出现长时间停顿的原因，如线程间死锁、死循环、请求外部资源导致的长时间等待等。 线程出现停顿的时候通过jstack来查看各个线程的调用堆栈，就可以知道没有响应的线程到底在后台做什么事情，或者等待什么资源。 命令格式 root@cv-console-rds-68784cdf9c-zk4d8:/# jstack -help Usage: jstack
记一次linux 内存占比过高
weixin_45835796的博客
07-19 1200
linux 服务器排查内存占比过高
分析Java核心转储
最佳 Java 编程
05-14 344
在本文中，我将向您展示如何调试Java核心文件，以查看导致JVM崩溃的原因。 我将使用在上一篇文章： 生成Java Core Dump中生成的核心文件。 您可以通过以下几种方法来诊断JVM崩溃： hs_err_pid日志文件 当JVM中发生致命错误时，通常会在进程的工作目录或操作系统的临时目录中生成一个名为hs_err_pidXXXX.log的错误日志文件。 该文件的顶部包含崩溃的原因和...
Java UnknownHostException –服务器的无效主机名–如何解决？
cunfen3485的博客
01-08 3257
An UnknownHostException的快速指南，如果在为远程方法调用创建到远程主机的连接时发生java.net.UnknownHostException，则会抛出该快速指南。 UnknownHostException的预防方法。 1.简介 在本教程中，我们将学习什么是UnknownHostException以及产生它的原因。 并且学习如何预防。 UnknownHostExceptio...
jstack用法
热门推荐
jack的博客
03-24 1万+
本文继续介绍Java自带的性能监测工具，本文使用jstack&nbsp;(Java Stack Trace)工具来玩~ 使用jstack命令工具可以得到线程堆栈信息，根据这些线程堆栈信息，我们可以去检查Java程序出现的问题，如检测死锁，并输出死锁的信息...
jstack的用途（简）
咸鱼的博客
07-21 1499
jstack作用：用于显示指定进程内线程的信息 语法：jstack [option] <pid> -F当’jstack [-l] pid’没有响应的时候强制打印栈信息,（如果直接jstack无响应时，用于强制jstack），一般情况不需要使用 -l长列表. 打印关于锁的附加信息,例如属于java.util.concurrent的ownable synchron...
JDK自带工具jstack使用简析
IT伪达人的专栏
03-11 1312
jstack是JDK自带的一款分析java线程代码栈的工具.使用它可以很方便的找到耗费cpu或者导致死锁的代码. jstack不但可以分析本地一个java进程,也可以分析远程主机上的java进程,还可以分析已生成的java core文件. 我认为,三个功能中最有用的是分析本地java进程.其余两个则不必要熟悉,既然有远程主机的访问权限,直接登录主机岂不更方便. 而java c
java进程 jstack
09-07
jstack是一个用于生成Java进程线程快照的工具。它可以帮助你分析线程的状态、堆栈跟踪和锁信息，以及识别可能的死锁情况。 要使用jstack命令，你需要知道Java进程的进程ID（PID）。然后，打开终端或命令提示符窗口...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值