Non‑Intrusive Method Timing and Tracing with Java Agent, Instrumentation and Bytecode Enhancement

In many projects developers insert repetitive timing code (e.g., using StopWatch ) directly into business methods, which is intrusive and hard to maintain. The article introduces Java Agent technology as a non‑intrusive solution, showing a minimal demo that leverages the java.lang.instrument.Instrumentation interface.

Instrumentation basics : Since JDK 1.5 the java.lang.instrument package provides methods such as addTransformer , retransformClasses , and isRetransformClassesSupported . Implementations of ClassFileTransformer can modify the bytecode of classes as they are loaded.

Agent entry points :

public static void premain(String agentArgs, Instrumentation inst) – executed before the application’s main method.

public static void agentmain(String agentArgs, Instrumentation inst) – executed when the agent is attached to a running JVM via the Attach API.

Demo for static timing : The article provides a MyClassFileTransformer that intercepts a target method, inserts calls to a TimeStatistics helper (start/end), and prints the elapsed time. The transformed class is packaged into an uber‑jar with a manifest specifying Premain‑Class and Agent‑Class .

Dynamic attachment : Using VirtualMachine.attach , the agent can be loaded into a running process. An example shows a PrintNumTest class that continuously prints 100 ; after attaching PrintNumAgent , the output changes to 50 without restarting the JVM.

Arthas integration : The article demonstrates how the Arthas trace command works internally. It parses interceptor annotations (e.g., @AtEnter , @AtExit ) and injects advice using ASM. The source code of TraceCommand , EnhancerCommand , and the bytecode transformation logic is examined, highlighting the registration of AdviceListener and the handling of native methods, JDK class filtering, and CGLIB proxies.

Bytekit simplification : Bytekit builds on ASM to provide a higher‑level API. An example shows a SampleInterceptor with @AtEnter , @AtExit , and @AtExceptionExit annotations that log method arguments, return values, and exceptions. The generated bytecode is compared with the original, illustrating the increase in complexity after instrumentation.

Overall, the article offers a comprehensive guide to using Java agents for performance monitoring, dynamic class redefinition, and tracing, supplemented with complete code listings and explanations of the underlying mechanisms.