https://docs.oracle.com/javase/8/docs/technotes/tools/unix/jsadebugd.html

The jsadebugd command attaches to a Java process or core file and acts as a debug server. Remote clients such as jstack, jmap, and jinfo can attach to the server through Java Remote Method Invocation (RMI). Before you start the jsadebugd command, start the RMI registry with the rmiregistry command as follows where $JAVA_HOME is the JDK installation directory:

rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar

sajdi.jar is no longer present and classes are linked in the image. The way to launch rmiregistry is to run rmiregistry (with no -J option).

This issue is filed to examine jsadebugd in jake works as expected.