{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidequjvtjnd7syylwvtcrwfek2pczunp3xbgbtqx5fbbwpxkegrzq",
    "uri": "at://did:plc:aolq4nwoeoi644iahuzsyn6l/app.bsky.feed.post/3miqgerwmrom2"
  },
  "path": "/2026/04/04/podcast-053/",
  "publishedAt": "2026-04-04T00:00:00.000Z",
  "site": "https://inside.java",
  "tags": [
    "HotSpot",
    "Serviceability"
  ],
  "textContent": "The Java tool jcmd (“j command”) sends diagnostic commands to the JVM, which will react by supplying the desired information: from finalizer queues to heap and thread dumps, from GC insights to virtual thread scheduler statistics. At the moment, this requires a running JVM, but once candidate is adopted, a lot of that information can be seamlessly extracted from a crashed JVM’s core dump, allowing easy post-mortem analysis.",
  "title": "Episode 53 “Analyzing Crashed JVMs” [IJN]",
  "updatedAt": "2026-04-04T00:00:00.000Z"
}