AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

java-diagnostics

Symptom-first runtime diagnostics for JVM applications using JDK tools: jcmd, jstack, jmap, jstat, JFR, GC logs, async-profiler, Native Memory Tracking, and Eclipse MAT. Use when a Java app has high CPU, memory leaks or OutOfMemoryError, slow startup, deadlocks or thread starvation, long GC pauses, native memory growth, or slow requests. Includes permission tiers for safe use.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--java-diagnostics at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 9

references/containers.md

Containers

Memory sizing

  • The JVM is container-aware (cgroup limits) in JDK 10+ and 8u191+.
  • Heap defaults to 25% of the container limit. Use -XX:MaxRAMPercentage=75.0 (or lower, e.g. 50-70, if there is significant native/off-heap usage) instead of a fixed -Xmx, so the heap scales with the limit.
  • Leave headroom for metaspace, thread stacks, code cache, direct buffers; an OOM-kill (exit code 137, OOMKilled) with a healthy heap points to native memory growth (see native-memory).
  • Verify what the JVM sees: java -XX:+PrintFlagsFinal -version | grep -E 'MaxHeapSize|MaxRAMPercentage|ActiveProcessorCount' and jcmd <pid> VM.flags.

Attaching tools

  • jcmd/jstack must run inside the container (same PID namespace and user): docker exec -it <c> jcmd 1 Thread.print, kubectl exec <pod> -- jcmd 1 Thread.print. JRE-only images lack these tools.
  • Do not rebuild production images to add tools. Prefer an ephemeral debug container sharing the process namespace (kubectl debug -it <pod> --image=<jdk-image> --target=<container>), and only with explicit consent.
  • Output files are written by the target JVM inside the container's filesystem; copy them out with kubectl cp / docker cp, then delete them in the container. Mind ephemeral storage limits for heap dumps.
  • Tier 1/2/3 rules apply unchanged; production pods require explicit user instruction.

CPU

Few CPUs or CFS throttling cause latency and GC thread starvation. Check -XX:ActiveProcessorCount, throttling metrics (container_cpu_cfs_throttled_seconds_total), and thread-pool sizing.

Debugging

See the java-debugging skill for JDWP port mapping to 127.0.0.1.