JVM 监控 - jps jstack jmap top jhat

2024-01-16 13:08
文章标签 java jvm top 监控 jmap jstack jps jhat

本文主要是介绍JVM 监控 - jps jstack jmap top jhat,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

  1. jps 查看 java 进程信息
  2. jstack 可查看java进程里的存活线程状态
  3. jmap 可查看java进程堆内存使用情况
  4. top linux 命令,可查看java某进程的线程
  5. jhat 可查看dump文件
  • jps  
    • jps 简单列出java进程 
[root@localhost app]# jps
5666 WatchdogServer
5746 XmlAppTransporterContext
5683 Bootstrap
10515 Jps
11929 XmlAppTransporterContext
11915 WatchdogServer

 

  • jstack 
    • jstack [pid] -> jstack 5666 列出指定进程下的线程情况
    • jstack [pid] | grep '关键字' -> jstack 5666 | grep 'RUNNABLE' 同上带有过滤
[root@localhost app]# jstack 5666
2019-04-04 16:10:28
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.181-b13 mixed mode):"Attach Listener" #30 daemon prio=9 os_prio=0 tid=0x00007f7998002800 nid=0x6bf7 waiting on condition [0x0000000000000000]java.lang.Thread.State: RUNNABLE"pool-4-thread-1" #29 prio=5 os_prio=0 tid=0x00007f798c04b000 nid=0x1664 waiting on condition [0x00007f79bd8d0000]java.lang.Thread.State: WAITING (parking)at sun.misc.Unsafe.park(Native Method)- parking to wait for  <0x00000000ca803bf8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)"JMX client heartbeat 3" #28 daemon prio=5 os_prio=0 tid=0x00007f798c041800 nid=0x1663 waiting on condition [0x00007f79bd9d1000]java.lang.Thread.State: TIMED_WAITING (sleeping)at java.lang.Thread.sleep(Native Method)at com.sun.jmx.remote.internal.ClientCommunicatorAdmin$Checker.run(ClientCommunicatorAdmin.java:175)at java.lang.Thread.run(Thread.java:748)"RMI RenewClean-[127.0.0.1:37134]" #27 daemon prio=5 os_prio=0 tid=0x00007f798c03f800 nid=0x165f in Object.wait() [0x00007f79bdad2000]java.lang.Thread.State: TIMED_WAITING (on object monitor)at java.lang.Object.wait(Native Method)at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)- locked <0x00000000ca7faaf0> (a java.lang.ref.ReferenceQueue$Lock)at sun.rmi.transport.DGCClient$EndpointEntry$RenewCleanThread.run(DGCClient.java:563)at java.lang.Thread.run(Thread.java:748)"input-stream-pool-1" #26 prio=5 os_prio=0 tid=0x00007f798c015800 nid=0x165b waiting on condition [0x00007f79bddde000]java.lang.Thread.State: WAITING (parking)at sun.misc.Unsafe.park(Native Method)- parking to wait for  <0x00000000ca7b5548> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)"input-stream-pool-0" #25 prio=5 os_prio=0 tid=0x00007f798c014000 nid=0x165a runnable [0x00007f79bdedf000]java.lang.Thread.State: RUNNABLEat java.io.FileInputStream.readBytes(Native Method)at java.io.FileInputStream.read(FileInputStream.java:255)at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)at java.io.BufferedInputStream.read(BufferedInputStream.java:345)- locked <0x00000000ca7c26c8> (a java.lang.UNIXProcess$ProcessPipeInputStream)at com.creditease.ns4.gear.watchdog.monitor.process.WatchdogChildProcess.readInputStream(WatchdogChildProcess.java:85)at com.creditease.ns4.gear.watchdog.monitor.process.WatchdogChildProcess.access$000(WatchdogChildProcess.java:38)at com.creditease.ns4.gear.watchdog.monitor.process.WatchdogChildProcess$1.run(WatchdogChildProcess.java:127)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)"DestroyJavaVM" #24 prio=5 os_prio=0 tid=0x00007f79dc00b000 nid=0x1623 waiting on condition [0x0000000000000000]java.lang.Thread.State: RUNNABLE

 

  • jmap 
    • jmap -heap [pid] -> jmap -heap 5666 列出指定进程的堆内存使用情况
[root@localhost app]# jmap -heap 5666
Attaching to process ID 5666, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 25.181-b13using parallel threads in the new generation.
using thread-local object allocation.
Concurrent Mark-Sweep GCHeap Configuration:MinHeapFreeRatio         = 40MaxHeapFreeRatio         = 70MaxHeapSize              = 1073741824 (1024.0MB)NewSize                  = 174456832 (166.375MB)MaxNewSize               = 174456832 (166.375MB)OldSize                  = 899284992 (857.625MB)NewRatio                 = 2SurvivorRatio            = 8MetaspaceSize            = 21807104 (20.796875MB)CompressedClassSpaceSize = 1073741824 (1024.0MB)MaxMetaspaceSize         = 17592186044415 MBG1HeapRegionSize         = 0 (0.0MB)Heap Usage:
New Generation (Eden + 1 Survivor Space):capacity = 157024256 (149.75MB)used     = 9306376 (8.875251770019531MB)free     = 147717880 (140.87474822998047MB)5.926712367291841% used
Eden Space:capacity = 139591680 (133.125MB)used     = 9306376 (8.875251770019531MB)free     = 130285304 (124.24974822998047MB)6.666855789686033% used
From Space:capacity = 17432576 (16.625MB)used     = 0 (0.0MB)free     = 17432576 (16.625MB)0.0% used
To Space:capacity = 17432576 (16.625MB)used     = 0 (0.0MB)free     = 17432576 (16.625MB)0.0% used
concurrent mark-sweep generation:capacity = 899284992 (857.625MB)used     = 2130744 (2.0320358276367188MB)free     = 897154248 (855.5929641723633MB)0.2369375691749563% used4999 interned Strings occupying 395840 bytes.
  • jmap -histo[:live] [pid] -> jmap -histo:live 5666 关键字live列出存活对象
 num     #instances         #bytes  class name
----------------------------------------------1:          8633         556016  [C2:          2168         245408  java.lang.Class3:          8621         206904  java.lang.String4:           544         188632  [B5:          1896         101440  [Ljava.lang.Object;6:           551          48488  java.lang.reflect.Method7:           873          48064  [I8:          1382          44224  java.util.HashMap$Node9:          1303          41696  java.util.concurrent.ConcurrentHashMap$Node10:           203          23200  [Ljava.util.HashMap$Node;11:          1143          18288  java.lang.Object12:           390          15600  java.lang.ref.SoftReference13:           429          14880  [Ljava.lang.String;14:            41          14704  [Ljava.util.concurrent.ConcurrentHashMap$Node;15:           395          12640  java.util.Hashtable$Entry16:           221          12376  java.lang.invoke.MemberName17:           480          11608  [Ljava.lang.Class;18:           239          11472  java.util.HashMap19:           341          10912  sun.misc.FDBigInteger20:            24           9024  java.lang.Thread21:           219           8760  java.util.LinkedHashMap$Entry22:           291           6984  java.lang.Long23:           206           6592  java.lang.invoke.LambdaForm$Name24:            74           6528  [Ljava.util.WeakHashMap$Entry;25:           102           6528  java.net.URL26:           158           6320  java.lang.invoke.MethodType27:            96           5760  [Ljava.lang.ref.SoftReference;28:            71           5680  java.lang.reflect.Constructor29:           229           5496  javax.management.ImmutableDescriptor30:            50           5448  [Ljava.util.Hashtable$Entry;31:           167           5344  java.lang.invoke.MethodType$ConcurrentWeakInternSet$WeakEntry32:           166           5312  com.sun.jmx.mbeanserver.ConvertingMethod33:           126           5040  java.util.WeakHashMap$Entry34:           279           4464  java.lang.Integer35:            67           4288  javax.management.openmbean.OpenMBeanAttributeInfoSupport36:           256           4096  java.lang.Byte37:           256           4096  java.lang.Short38:           102           4080  java.lang.ref.Finalizer39:           123           3936  java.lang.ref.WeakReference40:            92           3680  java.util.TreeMap$Entry41:            71           3408  java.util.WeakHashMap42:            71           3408  java.util.logging.LogManager$LoggerWeakRef43:            68           3264  java.lang.invoke.LambdaForm44:            73           3248  [Ljava.lang.invoke.LambdaForm$Name;45:           173           3144  [Lcom.sun.jmx.mbeanserver.MXBeanMapping;46:            94           3008  java.lang.ref.ReferenceQueue47:            54           2968  [Ljavax.management.MBeanAttributeInfo;
  • class name 列说明
B  byte 
C  char 
D  double 
F  float 
I  int 
J  long 
Z  boolean 
[  数组,如[I表示int[] [L+类名 其他对象
  • jmap -dump:format=b,file=[filename] [pid] -> jmap -dump:format=b,file=./dump.dat 5666 给指定进程生成dump
  • jhat -port 9999 ./dump.dat 查看生成的dump,浏览器打开:http://localhost:9999

上面图片是引用其他文章-Other Queries 最后一项支持OQL(对象查询语言)

这篇关于JVM 监控 - jps jstack jmap top jhat的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/612701

相关文章

Spring Boot 实现 IP 限流的原理、实践与利弊解析

《SpringBoot实现IP限流的原理、实践与利弊解析》在SpringBoot中实现IP限流是一种简单而有效的方式来保障系统的稳定性和可用性,本文给大家介绍SpringBoot实现IP限... 目录一、引言二、IP 限流原理2.1 令牌桶算法2.2 漏桶算法三、使用场景3.1 防止恶意攻击3.2 控制资源

Mac系统下卸载JAVA和JDK的步骤

《Mac系统下卸载JAVA和JDK的步骤》JDK是Java语言的软件开发工具包,它提供了开发和运行Java应用程序所需的工具、库和资源,:本文主要介绍Mac系统下卸载JAVA和JDK的相关资料,需... 目录1. 卸载系统自带的 Java 版本检查当前 Java 版本通过命令卸载系统 Java2. 卸载自定

springboot下载接口限速功能实现

《springboot下载接口限速功能实现》通过Redis统计并发数动态调整每个用户带宽,核心逻辑为每秒读取并发送限定数据量,防止单用户占用过多资源,确保整体下载均衡且高效,本文给大家介绍spring... 目录 一、整体目标 二、涉及的主要类/方法✅ 三、核心流程图解(简化) 四、关键代码详解1️⃣ 设置

Java Spring ApplicationEvent 代码示例解析

《JavaSpringApplicationEvent代码示例解析》本文解析了Spring事件机制,涵盖核心概念(发布-订阅/观察者模式)、代码实现(事件定义、发布、监听)及高级应用(异步处理、... 目录一、Spring 事件机制核心概念1. 事件驱动架构模型2. 核心组件二、代码示例解析1. 事件定义

SpringMVC高效获取JavaBean对象指南

《SpringMVC高效获取JavaBean对象指南》SpringMVC通过数据绑定自动将请求参数映射到JavaBean,支持表单、URL及JSON数据,需用@ModelAttribute、@Requ... 目录Spring MVC 获取 JavaBean 对象指南核心机制:数据绑定实现步骤1. 定义 Ja

javax.net.ssl.SSLHandshakeException:异常原因及解决方案

《javax.net.ssl.SSLHandshakeException:异常原因及解决方案》javax.net.ssl.SSLHandshakeException是一个SSL握手异常,通常在建立SS... 目录报错原因在程序中绕过服务器的安全验证注意点最后多说一句报错原因一般出现这种问题是因为目标服务器

Java实现删除文件中的指定内容

《Java实现删除文件中的指定内容》在日常开发中,经常需要对文本文件进行批量处理,其中,删除文件中指定内容是最常见的需求之一,下面我们就来看看如何使用java实现删除文件中的指定内容吧... 目录1. 项目背景详细介绍2. 项目需求详细介绍2.1 功能需求2.2 非功能需求3. 相关技术详细介绍3.1 Ja

springboot项目中整合高德地图的实践

《springboot项目中整合高德地图的实践》:本文主要介绍springboot项目中整合高德地图的实践,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一:高德开放平台的使用二:创建数据库(我是用的是mysql)三:Springboot所需的依赖(根据你的需求再

spring中的ImportSelector接口示例详解

《spring中的ImportSelector接口示例详解》Spring的ImportSelector接口用于动态选择配置类,实现条件化和模块化配置,关键方法selectImports根据注解信息返回... 目录一、核心作用二、关键方法三、扩展功能四、使用示例五、工作原理六、应用场景七、自定义实现Impor

SpringBoot3应用中集成和使用Spring Retry的实践记录

《SpringBoot3应用中集成和使用SpringRetry的实践记录》SpringRetry为SpringBoot3提供重试机制,支持注解和编程式两种方式,可配置重试策略与监听器,适用于临时性故... 目录1. 简介2. 环境准备3. 使用方式3.1 注解方式 基础使用自定义重试策略失败恢复机制注意事项