How vbforge/deadlock-visualizer works
Deadlock Visualizer is an interactive teaching application: a browser starts or clears a real ABBA deadlock scenario, polls its status, and displays thread/lock details and a live dependency graph. The backend owns scenario lifecycle and lock allocation, while a JVM probe supplies thread and deadlock observations used in the JSON snapshot. README documents diagnostic and Actuator endpoints as additional capabilities. Source excerpts support the central calls; template wiring and Actuator implementation details are documented but not excerpted.
Main entry points: DeadlockEngine.java Scenario lifecycle · index.html Visualizer page · DeadlockController.java Deadlock REST API · ThreadMxBeanProbe.java Thread MXBean probe
Components 15
Browser presentation
- Visualizer page
src/main/resources/templates/index.html - Polling and controls
src/main/resources/static/js/deadlock.js - Lock graph renderer
src/main/resources/static/js/lockGraph.js - Page styling
src/main/resources/static/css/app.css
Web interface
- Home page handler
src/main/java/com/vbforge/deadlock/web/HomeController.java - Deadlock REST API
src/main/java/com/vbforge/deadlock/web/DeadlockController.java
Scenario engine
- Scenario lifecycle
src/main/java/com/vbforge/deadlock/engine/DeadlockEngine.java - Scenario lock pair
src/main/java/com/vbforge/deadlock/engine/LockRegistry.java - Scenario status
src/main/java/com/vbforge/deadlock/engine/DeadlockStatus.java
JVM inspection and contract
- Thread MXBean probe
src/main/java/com/vbforge/deadlock/engine/ThreadMxBeanProbe.java - Status snapshot
src/main/java/com/vbforge/deadlock/engine/dto/DeadlockSnapshot.java - Thread details
src/main/java/com/vbforge/deadlock/engine/dto/ThreadSnapshot.java
Other components
- User browser
- JVM thread management
- Actuator endpoints
Connections 21
- User browser → Visualizer page: opens page
README.md - Home page handler → Visualizer page: renders
README.md - Visualizer page → Polling and controls: loads script
README.md - Visualizer page → Lock graph renderer: loads script
README.md - Visualizer page → Page styling: loads styles
README.md - User browser → Polling and controls: uses controls
README.md - Polling and controls → Deadlock REST API: requests status
src/main/resources/static/js/deadlock.js - Polling and controls → Lock graph renderer: delegates render
README.md - Deadlock REST API → Scenario lifecycle: invokes lifecycle
src/main/java/com/vbforge/deadlock/web/DeadlockController.java - Deadlock REST API → Scenario lock pair: reads lock names
src/main/java/com/vbforge/deadlock/web/DeadlockController.java - Scenario lifecycle → Scenario lock pair: rotates and reads
src/main/java/com/vbforge/deadlock/engine/DeadlockEngine.java - Scenario lifecycle → Thread MXBean probe: queries threads
src/main/java/com/vbforge/deadlock/engine/DeadlockEngine.java - Scenario lifecycle → Scenario status: updates state
src/main/java/com/vbforge/deadlock/engine/DeadlockEngine.java - Scenario lifecycle → Status snapshot: builds snapshot
src/main/java/com/vbforge/deadlock/engine/DeadlockEngine.java - Thread MXBean probe → JVM thread management: inspects threads
src/main/java/com/vbforge/deadlock/engine/ThreadMxBeanProbe.java - Thread MXBean probe → Scenario lock pair: names monitors
src/main/java/com/vbforge/deadlock/engine/ThreadMxBeanProbe.java - Thread MXBean probe → Thread details: builds details
src/main/java/com/vbforge/deadlock/engine/ThreadMxBeanProbe.java - Status snapshot → Scenario status: includes status
src/main/java/com/vbforge/deadlock/engine/dto/DeadlockSnapshot.java - Status snapshot → Thread details: contains details
src/main/java/com/vbforge/deadlock/engine/dto/DeadlockSnapshot.java - Deadlock REST API → JVM thread management: diagnoses threads
src/main/java/com/vbforge/deadlock/web/DeadlockController.java - User browser → Actuator endpoints: requests diagnostics
README.md