NAME
jsadebugd - serviceability agent debug daemon
SYNOPSIS
jjssaaddeebbuuggdd [pid] [server-id]
jjssaaddeebbuuggdd executable core [server-id]
DESCRIPTION
jjssaaddeebbuuggdd 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 using Java Remote Method Invocation (RMI). Before startingjsadebugd, rmiregistry must be started with:
rrmmiirreeggiissttrryy -JJ-XXbboooottccllaassssppaatthh//pp::$$JJAAVVAAHHOOMMEE//lliibb//ssaajjddii..jjaarr
where $JAVAHOME is the J2SE SDK installation directory. If rmireg-
istry was not started, jsadebugd will start an rmiregistry in a stan-
dard (1099) port internally. Debug server may be stopped by sendingSIGINT (pressing Ctrl-C) to it.
NNOOTTEE - This utility is unsupported and may or may not be available in
future versions of the J2SE SDK. jjiinnffoo is not currently available on Windows platforms or on the Linux Itanium platform. PPAARRAAMMEETTEERRSS pid process id of the process to which the debug server should attach. The process must be a Java process. To get a list of Java processes running on a machine, jps may be used. At most one instance of the debug server may be attached to a single 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 are
started on the same machine. This ID must be used by remote clients to identify the particular debug server to attach. Within a single machine, this ID must be unique.SEE ALSO
jjiinnffoo(1) jjmmaapp(1) jjppss(1) jjssttaacckk(1) rrmmiirreeggiissttrryy(1)13 June 2004 jsadebugd(1)