blob: df7a26ff2fb9ad61d0f3319c05ddd4de48c46953 [file] [log] [blame]
J. Duke319a3b92007-12-01 00:00:00 +00001.'" t
2." Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
3." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
4."
5." This code is free software; you can redistribute it and/or modify it
6." under the terms of the GNU General Public License version 2 only, as
7." published by the Free Software Foundation.
8."
9." This code is distributed in the hope that it will be useful, but WITHOUT
10." ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
11." FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
12." version 2 for more details (a copy is included in the LICENSE file that
13." accompanied this code).
14."
15." You should have received a copy of the GNU General Public License version
16." 2 along with this work; if not, write to the Free Software Foundation,
17." Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
18."
19." Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
20." CA 95054 USA or visit www.sun.com if you need additional information or
21." have any questions.
22." `
23.TH jps 1 "06 Aug 2006"
24." Generated by html2man
25
26.LP
27.SH NAME
28jps \- Java Virtual Machine Process Status Tool
29.LP
30.SH "SYNOPSIS"
31.LP
32
33.LP
34.nf
35\f3
36.fl
37\fP\f3jps\fP [ \f2options\fP ] [ \f2hostid\fP ]
38.br
39
40.fl
41.fi
42
43.LP
44.SH "PARAMETERS"
45.LP
46
47.LP
48.TP 3
49options
50Command\-line options.
51.TP 3
52hostid
53The host identifier of the host for which the process report should be generated. The \f2hostid\fP may include optional components that indicate the communications protocol, port number, and other implementation specific data.
54.LP
55.SH "DESCRIPTION"
56.LP
57
58.LP
59.LP
60The \f3jps\fP tool lists the instrumented HotSpot Java Virtual Machines (JVMs) on the target system. The tool is limited to reporting information on JVMs for which it has the access permissions.
61.LP
62.LP
63If \f3jps\fP is run without specifying a \f2hostid\fP, it will look for instrumented JVMs on the local host. If started with a \f2hostid\fP, it will look for JVMs on the indicated host, using the specified protocol and port. A \f3jstatd\fP process is assumed to be running on the target host.
64.LP
65.LP
66The \f3jps\fP command will report the local VM identifier, or \f2lvmid\fP, for each instrumented JVM found on the target system. The \f3lvmid\fP is typically, but not necessarily, the operating system's process identifier for the JVM process. With no options, \f3jps\fP will list each Java application's \f2lvmid\fP followed by the short form of the application's class name or jar file name. The short form of the class name or JAR file name omits the class's package information or the JAR files path information.
67.LP
68.LP
69The \f3jps\fP command uses the \f3java\fP launcher to find the class name and arguments passed to the \f2main\fP method. If the target JVM is started with a custom launcher, the class name (or JAR file name) and the arguments to the \f2main\fP method will not be available. In this case, the \f3jps\fP command will output the string \f2Unknown\fP for the class name or JAR file name and for the arguments to the main method.
70.LP
71.LP
72The list of JVMs produced by the \f3jps\fP command may be limited by the permissions granted to the principal running the command. The command will only list the JVMs for which the principle has access rights as determined by operating system specific access control mechanisms.
73.LP
74.LP
75\f3NOTE:\fP This utility is unsupported and may not be available in future versions of the JDK. It is not currently available on Windows 98 and Windows ME platforms.
76.LP
77.SH "OPTIONS"
78.LP
79
80.LP
81.LP
82The \f3jps\fP command supports a number of options that modify the output of the command. These options are subject to change or removal in the future.
83.LP
84.TP 3
85\-q
86Suppress the output of the class name, JAR file name, and arguments passed to the \f2main\fP method, producing only a list of local VM identifiers.
87.TP 3
88\-m
89Output the arguments passed to the main method. The output may be null for embedded JVMs.
90.TP 3
91\-l
92Output the full package name for the application's main class or the full path name to the application's JAR file.
93.TP 3
94\-v
95Output the arguments passed to the JVM.
96.TP 3
97\-V
98Output the arguments passed to the JVM through the flags file (the .hotspotrc file or the file specified by the \-XX:Flags=<\f2filename\fP> argument).
99.TP 3
100\-Joption
101Pass \f2option\fP to the \f3java\fP launcher called by \f3jps\fP. For example, \f3\-J\-Xms48m\fP sets the startup memory to 48 megabytes. It is a common convention for \f3\-J\fP to pass options to the underlying VM executing applications written in Java.
102.LP
103.SS
104HOST IDENTIFIER
105.LP
106.RS 3
107
108.LP
109.LP
110The host identifier, or \f2hostid\fP is a string that indicates the target system. The syntax of the \f2hostid\fP string largely corresponds to the syntax of a URI:
111.LP
112.nf
113\f3
114.fl
115[\fP\f4protocol\fP\f3:][[//]\fP\f4hostname\fP\f3][:\fP\f4port\fP\f3][/\fP\f4servername\fP\f3]\fP
116.br
117\f3
118.fl
119\fP
120.fi
121
122.LP
123.TP 3
124protocol
125The communications protocol. If the \f2protocol\fP is omitted and a \f2hostname\fP is not specified, the default protocol is a platform specific, optimized, local protocol. If the \f2protocol\fP is omitted and a \f2hostname\fP is specified, then the default protocol is \f3rmi\fP.
126.TP 3
127hostname
128A hostname or IP address indicating the target host. If \f2hostname\fP is omitted, then the target host is the local host.
129.TP 3
130port
131The default port for communicating with the remote server. If the \f2hostname\fP is omitted or the \f2protocol\fP specifies an optimized, local protocol, then \f2port\fP is ignored. Otherwise, treatment of the \f2port\fP parameter is implementation specific. For the default \f3rmi\fP protocol the \f2port\fP indicates the port number for the rmiregistry on the remote host. If \f2port\fP is omitted, and \f2protocol\fP indicates \f3rmi\fP, then the default rmiregistry port (1099) is used.
132.TP 3
133servername
134The treatment of this parameter depends on the implementation. For the optimized, local protocol, this field is ignored. For the \f3rmi\fP protocol, this parameter is a string representing the name of the RMI remote object on the remote host. See the \f3\-n\fP option for the \f3jstatd\fP command.
135.LP
136.RE
137.SH "OUTPUT FORMAT"
138.LP
139
140.LP
141.LP
142The output of the \f3jps\fP command follows the following pattern:
143.LP
144.nf
145\f3
146.fl
147\fP\f4lvmid\fP\f3 [ [ \fP\f4classname\fP\f3 | \fP\f4JARfilename\fP\f3 | "Unknown"] [ \fP\f4arg\fP\f3* ] [ \fP\f4jvmarg\fP\f3* ] ]\fP
148.br
149\f3
150.fl
151\fP
152.fi
153
154.LP
155.LP
156Where all output tokens are separated by white space. An \f2arg\fP that includes embedded white space will introduce ambiguity when attempting to map arguments to their actual positional parameters.
157.br
158.br
159\f3NOTE\fP: You are advised not to write scripts to parse \f3jps\fP output since the format may change in future releases. If you choose to write scripts that parse \f3jps\fP output, expect to modify them for future releases of this tool.
160.br
161
162.LP
163.SH "EXAMPLES"
164.LP
165
166.LP
167.LP
168This section provides examples of the \f3jps\fP command.
169.LP
170.LP
171Listing the instrumented JVMs on the local host:
172.LP
173.nf
174\f3
175.fl
176\fP\f3jps\fP
177.br
178
179.fl
18018027 Java2Demo.JAR
181.br
182
183.fl
18418032 jps
185.br
186
187.fl
18818005 jstat
189.br
190
191.fl
192.fi
193
194.LP
195.LP
196Listing the instrumented JVMs on a remote host:
197.LP
198.LP
199This example assumes that the \f3jstat\fP server and either the its internal RMI registry or a separate external \f3rmiregistry\fP process are running on the remote host on the default port (port 1099). It also assumes that the local host has appropriate permissions to access the remote host. This example also includes the \f2\-l\fP option to output the long form of the class names or JAR file names.
200.LP
201.nf
202\f3
203.fl
204\fP\f3jps \-l remote.domain\fP
205.br
206
207.fl
2083002 /opt/j2sdk1.5.0/demo/jfc/Java2D/Java2Demo.JAR
209.br
210
211.fl
2122857 sun.tools.jstatd.jstatd
213.br
214
215.fl
216.fi
217
218.LP
219.LP
220Listing the instrumented JVMs on a remote host with a non\-default port for the RMI registry
221.LP
222.LP
223This example assumes that the \f3jstatd\fP server, with an internal RMI registry bound to port 2002, is running on the remote host. This example also uses the \f2\-m\fP option to include the arguments passed to the \f2main\fP method of each of the listed Java applications.
224.LP
225.nf
226\f3
227.fl
228\fP\f3jps \-m remote.domain:2002\fP
229.br
230
231.fl
2323002 /opt/j2sdk1.5.0/demo/jfc/Java2D/Java2Demo.JAR
233.br
234
235.fl
2363102 sun.tools.jstatd.jstatd \-p 2002
237.fl
238.fi
239
240.LP
241.SH "SEE ALSO"
242.LP
243.RS 3
244.TP 2
245o
246java \- the Java Application Launcher
247.TP 2
248o
249jstat \- the Java virtual machine Statistics Monitoring Tool
250.TP 2
251o
252jstatd \- the jstat daemon
253.TP 2
254o
255rmiregistry \- the Java Remote Object Registry
256.RE
257
258.LP
259
260.LP
261