Tagged articles
jmap
18 articles · Page 1 of 1
This article explains how to differentiate memory leaks from out‑of‑memory errors, identifies classic GC‑based leak signals, introduces a toolchain (jstat, jmap, MAT, Arthas, JProfiler), walks through a step‑by‑step investigation workflow, lists common leak patterns, presents a real‑world ThreadLocal leak case, and offers preventive measures such as monitoring, regular heap dumps, code review, and stress testing.
ArthasGCJava
0 likes · 9 min read

This guide explains why frequent garbage collection and heap memory overflow occur in Java applications, demonstrates how to reproduce the issue with a sample program, and walks through various techniques—including jmap histograms, heap dumps, VisualVM analysis, and remote JMX monitoring—to diagnose and resolve out‑of‑memory errors.
Heap DumpJavaVisualVM
0 likes · 9 min read

This guide explains how to use JDK command-line utilities such as jps, jstat, jinfo, jmap, jhat, and jstack to monitor JVM processes, inspect memory usage, generate heap dumps, and diagnose performance issues, providing command syntax, options, and practical examples.
command-line-toolsjmapjps
0 likes · 8 min read

This article introduces core JVM performance and monitoring utilities—including jps, jstack, jmap, jhat, jstat, and hprof—explains their command syntax, demonstrates practical steps to locate high‑CPU threads, analyze heap dumps, and interpret GC statistics, and provides concrete code examples for Java developers.
JVMJavaPerformance Tuning
0 likes · 13 min read

This guide explains where Java's command‑line tools reside, why they are small wrappers around tools.jar, and provides detailed usage, options, and examples for the most common diagnostics utilities—including jps, jstat, jinfo, jmap, jhat, and jstack—helping developers monitor and troubleshoot JVM processes effectively.
JDKdiagnostic toolsjmap
0 likes · 7 min read

The article walks through a real‑world Java production incident where CPU spiked to 100%, detailing systematic troubleshooting steps, heap analysis with MAT, and the discovery that repeatedly creating BouncyCastleProvider objects caused a memory leak that was fixed by refactoring the code.
BouncyCastleCPU usageMemory Leak
0 likes · 6 min read

This article introduces a collection of essential Java tools—including jstack, jmap, jhat, jstat, jdb, jcmd, jps, jinfo, javap, javac, jconsole, and jvisualvm—explaining their purposes, common commands, and how they help diagnose memory leaks, CPU spikes, thread issues, and overall JVM performance.
DebuggingJavajhat
0 likes · 7 min read

This article explains common JVM problems such as OutOfMemoryError, memory leaks, and thread deadlocks, then introduces core monitoring tools—jps, jstack, jmap/jhat, jstat, and hprof—detailing their syntax, options, and practical examples to help Java developers diagnose and tune production applications.
HprofJVMjmap
0 likes · 15 min read

This article explains how to generate a heap dump with jmap, import it into Eclipse Memory Analyzer (MAT), and interpret the various reports such as Histogram, Dominator Tree, Top Consumers, and Leak Suspects to identify memory leaks or insufficient heap sizing in Java applications.
Heap DumpJavaMAT
0 likes · 8 min read

This guide explains multiple ways to capture Java heap dumps—including jmap, JVM flags, jcmd, JVisualVM, JMX, and programmatic methods—detailing command syntax, best‑practice options, and step‑by‑step procedures for effective memory‑issue diagnosis.
Heap DumpJVisualVMjcmd
0 likes · 6 min read

This guide introduces essential JVM performance monitoring tools—including jps, jstack, jmap, jhat, jstat, and hprof—explains their command syntax, demonstrates step‑by‑step usage with real‑world examples, and shows how to interpret their output to diagnose memory leaks, thread issues, GC behavior, and CPU hotspots.
HprofJVMPerformance Monitoring
0 likes · 14 min read

This article introduces the most common JVM performance problems in enterprise Java applications and provides a practical guide to using core monitoring and tuning tools such as jps, jstack, jmap, jstat and hprof, complete with command syntax, sample outputs and step‑by‑step troubleshooting examples.
JVMJavaMonitoring Tools
0 likes · 13 min read

After observing a Java process with persistently high memory usage, the article details a step‑by‑step investigation using top, ps, GC logging, and jmap to identify a memory leak caused by a third‑party jar, and shows how adjusting JVM parameters and fixing the code resolved the issue.
CMSGCMemory Leak
0 likes · 6 min read

The article walks through diagnosing a Java memory leak by examining Full GC symptoms, using jstat, jmap, and BTrace to identify excessive Hashtable entries, tracing the offending code, and preparing for targeted optimization.
BTraceBackendJava
0 likes · 3 min read

This article explains how to identify and resolve intermittent high CPU usage in Java/Tomcat services by analyzing thread stacks with jstack, examining GC behavior with Jstat, and using Jmap for memory inspection, providing step‑by‑step commands and practical tips for ops engineers.
CPUJavaTomcat
0 likes · 7 min read

Learn how to diagnose and resolve common Java performance issues such as OutOfMemoryError, thread deadlocks, and high CPU usage by using built‑in JVM tools—including jps, jstack, jmap, jhat, jstat, and hprof—through detailed command examples, output explanations, and practical profiling techniques.
JVMJavaMonitoring Tools
0 likes · 11 min read

The article explains how a Spring MVC service bean was duplicated across root and child WebApplicationContexts, causing a null‑injected instance that triggered a NullPointerException, and shows how JMap and JHat were used to locate the two beans and resolve the issue by adjusting component‑scan filters or removing the @Service annotation.
DebuggingJavaSpring MVC
0 likes · 14 min read

This guide walks IT operations engineers through systematic Linux‑based techniques for pinpointing Java processes that consume excessive CPU or memory, using tools like top, ps, jstack and jmap, and provides concrete steps to analyze and remediate the underlying code.
CPUJavaLinux
0 likes · 10 min read
