About this episode
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.
Get every episode summarized
Each time Inside Java publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Inside Java
"Make Java Safer with Flexible Constructor Bodies" [IJN]
Inside Java
"Ask the Architects at JavaOne'26" [AtA]
Inside Java
"You Must Avoid Final Field Mutation" [IJN]
Inside Java
"How JDK 26 Improves G1's Throughput" [AtA]
Inside Java