JCMD Try It
Supports Java by sending diagnostic commands to running JVMs for troubleshooting, monitoring, and performance analysis.
Version
Latest known: 24.0.2.0 (2025-07-24)
Latest known: 24.0.2.0 (2025-07-24)
Examples
2. List possible options available (based on PID)
c:\Program Files\Java\jdk-24\bin\jcmd.exe 17088 help
3. List all VM arguments used, either given by us or used default by JVM
c:\Program Files\Java\jdk-24\bin\jcmd.exe 17088 VM.flags
Try it
- List all Java processes on the host
Run jcmd -l to enumerate every Java process the current user can see (PID and main class / jar). This is the modern replacement for the older 'jps' tool. Useful as a first step before sending a diagnostic command to a specific JVM - you need the PID to address it. - Inspect this CF server's own JVM version
Discover the PID of the JVM currently running this very ColdFusion server (via java.lang.management.ManagementFactory.getRuntimeMXBean().getName(), which returns PID@hostname), then run 'jcmd <pid> VM.version' against it. Shows you the runtime version, build, and vendor that's hosting cfExec.com itself. - List diagnostic commands available on this JVM
After discovering this server's own JVM PID (same trick as the VM.version demo), run 'jcmd <pid> help' to enumerate every diagnostic command the JVM exposes. The list varies by JDK version and vendor - newer OpenJDKs add commands like JFR.start, GC.heap_info, Thread.print, and VM.system_properties.
Agree to terms to run demos.