Using DIXY
CLI Commands
Every dixy terminal command and dixy> shell command, with options.
Terminal commands
| Command | What it does |
|---|---|
dixy | Open the interactive dixy> shell. |
dixy detect --pid <pid> | Attach the agent to a running JVM and scan every second. |
dixy detect --jar <path> | Launch a jar with the agent attached and scan it. |
dixy detect --jar <path> --json | Same scan, machine-readable {"cycles":[...]} snapshots. |
dixy <app-directory> | Pick a runnable jar in the folder, start it with the agent, open the shell. |
dixy --version | Print the installed version. |
Shell commands
Run these at the dixy> prompt. Type help for options; tab completion is available.
| Command | What it does |
|---|---|
detect | Continuously scan live telemetry (supports --pid, --jar, --json). |
status | Diagnostic status: HEALTHY / WARNING / CRITICAL. |
deadlocks detect | Run detection once on the current wait-for graph. |
deadlocks list | List the latest stored deadlock reports. |
deadlocks clear | Clear all stored DIXY telemetry data. |
threads list | List registered threads. |
threads get --thread-id <id> | Get a thread by JVM thread id. |
threads delete --id <id> | Delete a thread by database id. |
locks list | List locks. |
locks get --lock-id <id> | Get a lock by its lock-id string. |
locks delete --id <id> | Delete a lock by database id. |
events list | Recent raw JVMTI events (LockOwned / LockReleased). |
help | List every command and its options. |
Run the shell without the launcher
bash
java -Duser.timezone=UTC -Dspring.profiles.active=cli \ -jar build/libs/virtual_deadlock_detection-0.0.1-SNAPSHOT.jarOn Windows, run-cli.bat builds the jar, starts PostgreSQL + Redis and launches the shell in one step.