0 views collected around this technical thread.
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.
The article recounts a weekend on‑call incident where a Java monitoring service suffered network packet loss and a severe memory leak, leading to massive timeouts, high CPU usage, and frequent GC, and explains how the problem was diagnosed and resolved using tools such as top, jstat, jstack, jmap, and MAT.
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.
This article reports a systematic experiment that compares four IntelliJ IDEA memory configurations on a large Java monolith and two micro‑services, measuring startup, project loading times and JVM garbage‑collection metrics with jstat to identify the most efficient setting.
This article explains the jstat command syntax, options, and detailed parameter descriptions for monitoring JVM class loading, memory usage, garbage collection, JIT compilation, and other runtime statistics, providing examples and visual tables to help developers analyze Java process performance.
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.