Java Cheatsheet - Java & JVM Command Reference
This reference is for developers writing Spring Boot/WAR apps or operating them in production: from compiling and packing with javac/java/jar, one-command builds with Maven/Gradle, heap sizing with -Xms/-Xmx, G1 GC and GC logging, to grabbing threads and heap with jstack/jmap/jstat when the service stalls. Unlike a generic command list, it is organized around building the service, running it stably, tuning it faster, and debugging its failures. After reading you should be able to complete a build → deploy → GC tune → deadlock hunt cycle on your own.
Compile & Run 6
javac Main.javajava -cp .:lib.jar Mainjava -cp ".;lib.jar" Mainjar cvf app.jar *.classjar tf app.jarjar xf app.jarMaven Commands 8
mvn cleanmvn compilemvn testmvn packagemvn installmvn dependency:treemvn -U clean packagemvn spring-boot:runGradle Commands 6
./gradlew build./gradlew clean./gradlew test./gradlew bootRun./gradlew dependencies./gradlew tasksJVM Flags & Tuning 6
java -Xms512m -Xmx2g -jar app.jarjava -XX:+UseG1GC -jar app.jarjava -XX:+PrintGCDetails -Xloggc:gc.logjava -XX:+HeapDumpOnOutOfMemoryErrorjava -XX:HeapDumpPath=/tmp/dump.hprofjava -verbose:gcJVM Troubleshooting 8
jps -ljstack <pid>jmap -heap <pid>jmap -dump:format=b,file=dump.hprof <pid>jstat -gcutil <pid> 1000jinfo <pid>jconsolevisualvmTips
- With jstack, look for "Found one Java-level deadlock" to spot deadlocks.
- Heap dump files can be huge - check disk space in production first.
- G1 GC suits large heaps (>6G); Parallel GC gives higher throughput on small heaps.
Official References
Each command links to its official documentation below, so you can verify the latest usage and read deeper.
Maintained by LaoHand
Publicly updated on Jul 21, 2026, continuously proofread against official docs.
Contact Us
Wrong command or description? Send us corrections, business inquiries or product feedback by email.
Contact Us