1jsadebugd(1)                General Commands Manual               jsadebugd(1)
2
3
4

Name

6       jsadebugd - Serviceability Agent Debug Daemon
7

SYNOPSIS

9       jsadebugd pid [ server-id ]
10       jsadebugd executable core [ server-id ]
11
12

PARAMETERS

14          pid
15             process  id  of  the  process  to  which  the debug server should
16             attach. The process must be a Java process. To get a list of Java
17             processes  running  on a machine, jps(1) may be used. At most one
18             instance of the debug server may be attached to a single process.
19
20          executable
21             Java executable from which the core dump was produced
22
23          core
24             Core file to which the debug server should attach.
25
26          server-id
27             Optional unique id, needed if multiple debug servers are  started
28             on  the  same  machine. This ID must be used by remote clients to
29             identify the particular debug server to attach. Within  a  single
30             machine, this ID must be unique.
31
32

DESCRIPTION

34       jsadebugd  attaches  to a Java process or core file and acts as a debug
35       server. Remote clients such as jstack(1),  jmap(1),  and  jinfo(1)  can
36       attach  to the server using Java Remote Method Invocation (RMI). Before
37       starting jsadebugd, rmiregistry @
38       http://docs.oracle.com/javase/7/docs/technotes/tools/index.html#rmi
39       must be started with:
40
41       rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar
42
43
44       where $JAVA_HOME is the JDK installation directory. If rmiregistry was
45       not started, jsadebugd will start an rmiregistry in a standard (1099)
46       port internally. Debug server may be stopped by sending SIGINT (press‐
47       ing Ctrl-C) to it.
48
49       NOTE - This utility is unsupported and may or may not be available in
50       future versions of the JDK. In Windows Systems where dbgeng.dll is not
51       present, 'Debugging Tools For Windows' needs to be installed to have
52       these tools working. Also, PATH environment variable should contain the
53       location of jvm.dll used by the target process or the location from
54       which the Crash Dump file was produced.
55
56       For example, set PATH=<jdk>\jre\bin\client;%PATH%
57

SEE ALSO

59          o jinfo(1)
60
61          o jmap(1)
62
63          o jps(1)
64
65          o jstack(1)
66
67          o rmiregistry @
68            http://docs.oracle.com/javase/7/docs/tech‐
69            notes/tools/index.html#rmi
70
71
72                                  16 Mar 2012                     jsadebugd(1)
Impressum