1jsadebugd(1) General Commands Manual jsadebugd(1)
2
3
4
6 jsadebugd - Serviceability Agent Debug Daemon
7
9 jsadebugd pid [ server-id ]
10 jsadebugd executable core [ server-id ]
11
12
14 pid
15 process id of the process to which the debug server should attach.
16 The process must be a Java process. To get a list of Java processes
17 running on a machine, jps may be used. At most one instance of the
18 debug server may be attached to a single process.
19
20 executable
21
22 Java executable from which the core dump was produced
23
24 core
25 Core file to which the debug server should attach.
26
27 server-id
28 Optional unique id, needed if multiple debug servers are started on
29 the same machine. This ID must be used by remote clients to identify
30 the particular debug server to attach. Within a single machine, this
31 ID must be unique.
32
34 jsadebugd attaches to a Java process or core file and acts as a debug
35 server. Remote clients such as jstack, jmap, and jinfo can attach to
36 the server using Java Remote Method Invocation (RMI). Before starting
37 jsadebugd, rmiregistry must be started with:
38
39 rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar
40
41
42 where $JAVA_HOME is the JDK installation directory. If rmiregistry was
43 not started, jsadebugd will start an rmiregistry in a standard (1099)
44 port internally. Debug server may be stopped by sending SIGINT (pressā
45 ing Ctrl-C) to it.
46
47 NOTE - This utility is unsupported and may or may not be available in
48 future versions of the JDK. jsadebugd is not currently available on
49 Windows platforms.
50
52 * jinfo
53
54 * jmap
55
56 * jps
57
58 * jstack
59
60 * rmiregistry
61
62
63 05 Aug 2006 jsadebugd(1)