The Story of a Java Class in the JVM

This article narrates the journey of a Java class called Account as it discovers the inner workings of the Java Virtual Machine (JVM). It uses a story‑like format to teach core JVM concepts.

Chapter 1 – The Stranger in a Police Uniform – A Classloader, dressed like a police officer, asks the class to identify itself. It checks the magic number 0xCAFEBABE and version numbers (50, 0), revealing that the class was compiled with JDK 1.6.

Chapter 2 – Information Gathering – The Classloader explains the hierarchy of classloaders: Bootstrap Classloader, Extension Classloader, and App Classloader. It describes how this hierarchy prevents malicious classes (e.g., a rogue java.lang.String) from being loaded before trusted core classes.

Chapter 3 – First Encounter with the Virtual Machine – The class is taken to the "Method Area" building, where it sees its fully qualified name com.mytaobao.domain.Account. It learns that the method area stores class metadata, constant pools, and field/method definitions.

Chapter 4 – Stack‑Based Execution – A thread (ID 0x3704) invokes the class’s add method. The story walks through the bytecode instructions: public void add(int x, int y) { x = x + y; /* ... */ } The thread executes iload_0, iload_1, iadd, and istore_0, illustrating how the operand stack (the "bucket") is used for loading, adding, and storing values.

The narrative explains that the JVM is a stack‑based machine, contrasting it with CPU registers that require many separate storage locations.

Chapter 5 – The Heap and Garbage Collection – The class visits the "Heap" building, where objects are stored. It meets "cleaners" (the garbage collector) that remove objects with a reference count of zero. The story mentions that heap size is determined by JVM launch parameters and that unreachable objects cause OutOfMemoryError.

Chapter 6 – Debugging and Breakpoints – When a developer steps through the code, the thread pauses at a breakpoint, illustrating how debugging slows execution dramatically compared to the JVM’s native speed.

Chapter 7 – Source Code Revelation – The class discovers its source file Account.java under C:\workspace\myTaobao\src\com\mytaobao\domain. Each recompilation overwrites the old .class file, and a bug is eventually found and fixed.

The article concludes with acknowledgments, a disclaimer about copyright, and a note that the story was created by a former IBM architect sharing programming experiences.