{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiejgojjmzgltxa2rbh6jifj5pd7e4hqfswdfsjqov724dw2rtc4gy",
    "uri": "at://did:plc:aolq4nwoeoi644iahuzsyn6l/app.bsky.feed.post/3milfgorrmtd2"
  },
  "path": "/2026/04/02/newscast-109/",
  "publishedAt": "2026-04-02T00: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 JEP 528 is adopted, a lot of that information can be seamlessly extracted from a crashed JVM's core dump, allowing easy post-mortem analysis.",
  "title": "Analyzing Crashed JVMs - Inside Java Newscast #109",
  "updatedAt": "2026-04-02T00:00:00.000Z"
}