jdiscript is an elegant wrapper for a more civilized Java Debugger Interface. It allows you
to write scripts that use the JDI to control and inspect almost anything happening inside a
running JVM. Think of it as similar to DTrace, but with
more Java-specific flexibility and the ability to use a JVM language for scripting.

Here’s how you’d print out a stack trace any time a thread tried to enter a
monitor already owned by another thread:

VirtualMachine vm = new VMSocketAttacher(12345).attach();
JDIScript j = new JDIScript(vm);
j.monitorContendedEnterRequest(e -> {
    j.printTrace(e, "ContendedEnter for "+e.monitor());
}).enable();
j.run();

For more, see the included examples.

jdiscript provides

• An event loop that frees you from the details of managing EventSets.

• A set of FunctionalInterfaces
  so you can use lambdas.

• Classes that handle the boilerplate of launching or attaching to a VirtualMachine.

• A JDIScript class that ties it all together and provides convenience methods for common script patterns.

jdiscript was originally focused on providing an API that you would use from languages like
Groovy, JRuby, or Clojure, under the belief that Java itself was too verbose for a nice
scripting experience. With Java 8, this has changed, and straight Java is now compact enough
that it might not be worth the overhead of switching to another language. All examples that
ship with jdiscript have been converted to Java 8.

Note: you need to have the jdk’s tools.jar on your classpath in order to use the JDI.