equal
deleted
inserted
replaced
1 ." Copyright (c) 2004, 2010, Oracle and/or its affiliates. All rights reserved. |
1 ." Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved. |
2 ." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. |
2 ." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. |
3 ." |
3 ." |
4 ." This code is free software; you can redistribute it and/or modify it |
4 ." This code is free software; you can redistribute it and/or modify it |
5 ." under the terms of the GNU General Public License version 2 only, as |
5 ." under the terms of the GNU General Public License version 2 only, as |
6 ." published by the Free Software Foundation. |
6 ." published by the Free Software Foundation. |
17 ." |
17 ." |
18 ." Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA |
18 ." Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA |
19 ." or visit www.oracle.com if you need additional information or have any |
19 ." or visit www.oracle.com if you need additional information or have any |
20 ." questions. |
20 ." questions. |
21 ." |
21 ." |
22 .TH jstatd 1 "02 Jun 2010" |
22 .TH jstatd 1 "10 May 2011" |
23 |
23 |
24 .LP |
24 .LP |
25 .SH "Name" |
25 .SH "Name" |
26 jstatd \- Virtual Machine jstat Daemon |
26 jstatd \- Virtual Machine jstat Daemon |
27 .LP |
27 .LP |
28 .SH "SYNOPSIS" |
28 .SH "SYNOPSIS" |
29 .LP |
29 .LP |
30 |
|
31 .LP |
|
32 .nf |
30 .nf |
33 \f3 |
31 \f3 |
34 .fl |
32 .fl |
35 jstatd [ \fP\f4options\fP\f3 ]\fP |
33 jstatd [ \fP\f4options\fP\f3 ]\fP |
36 .br |
34 .br |
39 \fP |
37 \fP |
40 .fi |
38 .fi |
41 |
39 |
42 .LP |
40 .LP |
43 .SH "PARAMETERS" |
41 .SH "PARAMETERS" |
44 .LP |
|
45 |
|
46 .LP |
42 .LP |
47 .RS 3 |
43 .RS 3 |
48 .TP 3 |
44 .TP 3 |
49 options |
45 options |
50 Command\-line options. The options may be in any order. If there are redundant or contradictory options, the last option specified will take precedence. |
46 Command\-line options. The options may be in any order. If there are redundant or contradictory options, the last option specified will take precedence. |
51 .RE |
47 .RE |
52 |
48 |
53 .LP |
49 .LP |
54 .SH "DESCRIPTION" |
50 .SH "DESCRIPTION" |
55 .LP |
51 .LP |
56 |
|
57 .LP |
|
58 .LP |
52 .LP |
59 The \f3jstatd\fP tool is an RMI server application that monitors for the creation and termination of instrumented HotSpot Java virtual machines (JVMs) and provides a interface to allow remote monitoring tools to attach to JVMs running on the local host. |
53 The \f3jstatd\fP tool is an RMI server application that monitors for the creation and termination of instrumented HotSpot Java virtual machines (JVMs) and provides a interface to allow remote monitoring tools to attach to JVMs running on the local host. |
60 .LP |
54 .LP |
61 .LP |
55 .LP |
62 The \f3jstatd\fP server requires the presence of an RMI registry on the local host. The \f3jstatd\fP server will attempt to attach to the RMI registry on the default port, or on the port indicated by the \f2\-p port\fP option. If an RMI registry is not found, one will be created within the \f3jstatd\fP application bound to the port indicated by the \f2\-p port\fP option or to the default RMI registry port if \f2\-p port\fP is omitted. Creation of an internal RMI registry can be inhibited by specifying the \f2\-nr\fP option. |
56 The \f3jstatd\fP server requires the presence of an RMI registry on the local host. The \f3jstatd\fP server will attempt to attach to the RMI registry on the default port, or on the port indicated by the \f2\-p port\fP option. If an RMI registry is not found, one will be created within the \f3jstatd\fP application bound to the port indicated by the \f2\-p port\fP option or to the default RMI registry port if \f2\-p port\fP is omitted. Creation of an internal RMI registry can be inhibited by specifying the \f2\-nr\fP option. |
63 .LP |
57 .LP |
64 .LP |
58 .LP |
65 \f3NOTE:\fP This utility is unsupported and may or may not be available in future versions of the JDK. It is not currently available on the Windows 98 and Windows ME platforms. |
59 \f3NOTE:\fP This utility is unsupported and may or may not be available in future versions of the JDK. It is not currently available on the Windows 98 and Windows ME platforms. |
66 .LP |
60 .LP |
67 .SH "OPTIONS" |
61 .SH "OPTIONS" |
68 .LP |
|
69 |
|
70 .LP |
62 .LP |
71 .LP |
63 .LP |
72 The \f3jstatd\fP command supports the following options: |
64 The \f3jstatd\fP command supports the following options: |
73 .LP |
65 .LP |
74 .RS 3 |
66 .RS 3 |
87 .RE |
79 .RE |
88 |
80 |
89 .LP |
81 .LP |
90 .SH "SECURITY" |
82 .SH "SECURITY" |
91 .LP |
83 .LP |
92 |
|
93 .LP |
|
94 .LP |
84 .LP |
95 The \f3jstatd\fP server can only monitor JVMs for which it has the appropriate native access permissions. Therefor the \f3jstatd\fP process must be running with the same user credentials as the target JVMs. Some user credentials, such as the \f2root\fP user in UNIX(TM) based systems, have permission to access the instrumentation exported by any JVM on the system. A \f3jstatd\fP process running with such credentials can monitor any JVM on the system, but introduces additional security concerns. |
85 The \f3jstatd\fP server can only monitor JVMs for which it has the appropriate native access permissions. Therefor the \f3jstatd\fP process must be running with the same user credentials as the target JVMs. Some user credentials, such as the \f2root\fP user in UNIX(TM) based systems, have permission to access the instrumentation exported by any JVM on the system. A \f3jstatd\fP process running with such credentials can monitor any JVM on the system, but introduces additional security concerns. |
96 .LP |
86 .LP |
97 .LP |
87 .LP |
98 The \f3jstatd\fP server does not provide any authentication of remote clients. Therefore, running a \f3jstatd\fP server process exposes the instrumentation export by all JVMs for which the \f3jstatd\fP process has access permissions to any user on the network. This exposure may be undesireable in your environment and local security policies should be considered before starting the \f3jstatd\fP process, particularly in production environments or on unsecure networks. |
88 The \f3jstatd\fP server does not provide any authentication of remote clients. Therefore, running a \f3jstatd\fP server process exposes the instrumentation export by all JVMs for which the \f3jstatd\fP process has access permissions to any user on the network. This exposure may be undesireable in your environment and local security policies should be considered before starting the \f3jstatd\fP process, particularly in production environments or on unsecure networks. |
100 .LP |
90 .LP |
101 The \f3jstatd\fP server installs an instance of RMISecurityPolicy if no other security manager has been installed and therefore requires a security policy file to be specified. The policy file must conform to the default policy implementation's |
91 The \f3jstatd\fP server installs an instance of RMISecurityPolicy if no other security manager has been installed and therefore requires a security policy file to be specified. The policy file must conform to the default policy implementation's |
102 .na |
92 .na |
103 \f2Policy File Syntax\fP @ |
93 \f2Policy File Syntax\fP @ |
104 .fi |
94 .fi |
105 http://java.sun.com/javase/6/docs/technotes/guides/security/PolicyFiles.html. |
95 http://download.oracle.com/javase/7/docs/technotes/guides/security/PolicyFiles.html. |
106 .LP |
96 .LP |
107 .LP |
97 .LP |
108 The following policy file will allow the \f3jstatd\fP server to run without any security exceptions. This policy is less liberal then granting all permissions to all codebases, but is more liberal than a policy that grants the minimal permissions to run the \f3jstatd\fP server. |
98 The following policy file will allow the \f3jstatd\fP server to run without any security exceptions. This policy is less liberal then granting all permissions to all codebases, but is more liberal than a policy that grants the minimal permissions to run the \f3jstatd\fP server. |
109 .LP |
99 .LP |
110 .nf |
100 .nf |
143 .LP |
133 .LP |
144 For sites with more restrictive security practices, it is possible to use a custom policy file to limit access to specific trusted hosts or networks, though such techniques are subject to IP addreess spoofing attacks. If your security concerns cannot be addressed with a customized policy file, then the safest action is to not run the \f3jstatd\fP server and use the \f3jstat\fP and \f3jps\fP tools locally. |
134 For sites with more restrictive security practices, it is possible to use a custom policy file to limit access to specific trusted hosts or networks, though such techniques are subject to IP addreess spoofing attacks. If your security concerns cannot be addressed with a customized policy file, then the safest action is to not run the \f3jstatd\fP server and use the \f3jstat\fP and \f3jps\fP tools locally. |
145 .LP |
135 .LP |
146 .SH "REMOTE INTERFACE" |
136 .SH "REMOTE INTERFACE" |
147 .LP |
137 .LP |
148 |
|
149 .LP |
|
150 .LP |
138 .LP |
151 The interface exported by the \f3jstatd\fP process is proprietary and is guaranteed to change. Users and developers are discouraged from writing to this interface. |
139 The interface exported by the \f3jstatd\fP process is proprietary and is guaranteed to change. Users and developers are discouraged from writing to this interface. |
152 .LP |
140 .LP |
153 .SH "EXAMPLES" |
141 .SH "EXAMPLES" |
154 .LP |
|
155 |
|
156 .LP |
142 .LP |
157 .LP |
143 .LP |
158 Here are some examples of starting \f3jstatd\fP. Note that the \f3jstatd\fP scripts automatically start the server in the background. |
144 Here are some examples of starting \f3jstatd\fP. Note that the \f3jstatd\fP scripts automatically start the server in the background. |
159 .LP |
145 .LP |
160 .SS |
146 .SS |
262 .TP 2 |
248 .TP 2 |
263 o |
249 o |
264 .na |
250 .na |
265 \f2rmiregistry\fP @ |
251 \f2rmiregistry\fP @ |
266 .fi |
252 .fi |
267 http://java.sun.com/javase/6/docs/technotes/tools/index.html#rmi \- the Java Remote Object Registry |
253 http://download.oracle.com/javase/7/docs/technotes/tools/index.html#rmi \- the Java Remote Object Registry |
268 .RE |
254 .RE |
269 |
255 |
270 .LP |
256 .LP |
271 |
257 |