Martijn Dashorst has worked since 2004 at Topicus and has used Java since 2002. Loves server-side Java. You might know him from Apache Wicket—he's dabbled somewhat in that framework. Loves his family and cats, finds Douglas Adams' description of the Sirius Cybernetics Corporation's technology very apt to the current technology landscape.
Your Java application is running smoothly, blissfully unaware of the danger lurking just around the corner. Then—without warning—it vanishes without a trace. Upon investigation, you discover the virtual remains of countless slain JVMs, each marked with the same cryptic number: 137. A serial killer is on the loose in your cluster.
This true crime investigation will walk you through the differences between JVM memory areas, the mechanics of container OOMKills, analysing Grafana dashboards for memory and thread anomalies, interpreting heap dumps, and utilising JVM Native Memory Tracking (NMT) to uncover hidden native memory consumption.
You’ll master practical forensic techniques and proven prevention strategies—from memory tuning tactics and balancing heap vs. non-heap allocations to leveraging large language models (LLMs) for advanced forensic analysis. These skills will help ensure your applications stay alive—even when something’s out to get them.
Just like in a real murder mystery, we may not know whodunnit... but with Martijn Dashorst leading the investigation, you're sure to get closer to the truth.
Searching for speaker images...