btrace

Trace method calls in a running Java application

$ btrace [pid] [script.java]

$ btrace -cp [/path/to/classes] [pid] [script.java]

$ btrace -u [pid] [script.java]

$ btracec [script.java]

$ btrace -v [pid] [script.java]

btrace [options] pid script
btracec [options] script

BTrace is a safe, dynamic tracing tool for the Java platform. It allows attaching tracing scripts to running Java applications without restarting them. BTrace scripts are written in Java with annotations defining trace points.
BTrace works by instrumenting bytecode of the target application. Scripts can intercept method entries, exits, exceptions, and other events. The tracing is designed to be safe, preventing scripts from modifying application state or causing deadlocks.
Common use cases include performance profiling, debugging production issues, monitoring method call patterns, and tracking memory allocations without application restarts.

pid

Process ID of target Java application.

BTrace script file (.java).

Verbose mode.

Unsafe mode (enables more operations).

Dump instrumented classes to path.

Probe descriptor search path.

Classpath for script compilation.

Preprocessor include path.

Agent server port.

Send metrics to StatsD server.

Target JVM must have similar or compatible Java version. Some operations are restricted in safe mode to prevent application harm. Cannot trace native methods. May have performance overhead on high-frequency methods. Requires write access to target application's process.

BTrace was created by A. Sundararajan at Sun Microsystems around 2007-2008 as a DTrace-inspired tool for Java. After Oracle's acquisition of Sun, the project became open source and community-maintained. It has been used extensively for production debugging and performance analysis of Java applications, filling a gap for dynamic instrumentation in the JVM ecosystem.

jstack(1), jmap(1), java(1), async-profiler(1)