jsadebugd - Serviceability Agent Debug Daemon
SYNOPSIS
jsadebugd pid [ server-id ]jsadebugd executable core [ server-id ]
PARAMETERS
- pid
- process id of the process to which the debug server shouldattach. The process must be a Java process. To get a list of Javaprocesses running on a machine,jps may beused. At most one instance of the debug server may be attached to asingle process.
- executable
- Java executable from which the core dump was produced
- core
- Core file to which the debug server should attach.
- server-id
- Optional unique id, needed if multiple debug servers arestarted on the same machine. This ID must be used by remote clientsto identify the particular debug server to attach. Within a singlemachine, this ID must be unique.
DESCRIPTION
jsadebugd attaches to a Java process or core file andacts as a debug server. Remote clients such asjstack,jmap, andjinfo can attach to the server using JavaRemote Method Invocation (RMI). Before startingjsadebugd,rmiregistrymust be started with:
rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jarwhere$JAVA_HOME is the JDK installation directory.If rmiregistry was not started, jsadebugd will start an rmiregistryin a standard (1099) port internally. Debug server may be stoppedby sending SIGINT (pressing Ctrl-C) to it.
NOTE - This utility is unsupported and may or may not beavailable in future versions of the JDK. In Windows Systems wheredbgeng.dll is not present, 'Debugging Tools For Windows' needs tobe installed to have these tools working. Also,PATHenvironment variable should contain the location ofjvm.dll used by the target process or the locationfrom which the Crash Dump file was produced.
For example,setPATH=<jdk>\jre\bin\client;%PATH%