Skip to content
Learn

JVM Internals & Concurrency

For Java 21 and Spring Boot engineers. Not only how the APIs work: how to diagnose and fix the production incidents they cause, with real thread dumps, GC logs and JFR output.
  1. Understand
  2. Simulate
  3. Run it for real
  4. Diagnose
  5. Fix
Start hereJVM architecture, class loading and bytecode execution

Your progress

0% · 0 / 19 lessons · 0 / 8 simulations

Today's JVM check

One a day

From Memory leaks and heap dumps

A service with -Xmx4g is restarted by its orchestrator about every 30 hours with OutOfMemoryError: Java heap space. After the heap was raised to 8 GB the restarts come about every 60 hours. Traffic has the same daily shape every day. Heap after full collection is 1.1 GB an hour after start and grows by about 130 MB per hour.

What is the right next step?

Learning paths

In order, or jump in

  1. Path 1: JVM Runtime and MemoryHow a class becomes running machine code, where every kind of memory lives, how objects are allocated, and what the JIT compiler does with hot code.
    0 / 4 lessons
  2. Path 2: Garbage Collection and DiagnosticsG1 and ZGC, reading pauses and allocation pressure from GC logs, finding leaks in heap dumps, and the three tools you reach for first: JFR, GC logs and async-profiler.
    0 / 4 lessons
  3. Path 3: Concurrency FoundationsThreads and the Java Memory Model, races, visibility and atomicity, and the tools that fix them: synchronized, volatile, locks and atomics. Then what goes wrong when threads wait on each other.
    0 / 6 lessons
  4. Path 4: Executors, Async and Virtual ThreadsThread pools and what happens when they fill, CompletableFuture, concurrent collections, ForkJoinPool, and virtual threads in Java 21: what they change and what they cannot.
    0 / 5 lessons

Break it, read the evidence, fix it

What runs in this page is a deterministic simulation, and is labelled so. Output labelled "Real JVM output" was copied from runs of OpenJDK 21 (Eclipse Temurin 21.0.13, Linux, 2 CPUs); the programs are in the repository under labs/jvm. Progress, bookmarks and notes are kept in this browser only.