JSTATD(1)
π
JSTATD(1) β the jstatd page π
okay so bestie, welcome to the jstatd manual page from the JDK Commands lineup π. This one is a little spicy because it's experimental, unsupported, and deprecated β but we're gonna get through it together, no cap β¨.
πΈ NAME πΈ
jstatd β monitor the creation and termination of instrumented Java HotSpot VMs
π SYNOPSIS π
WARNING: This command is experimental, unsupported, and deprecated. It will be removed in a future release.
jstatd [options]
Here, options is literally the jstatd command-line options. See Options for the jstatd Command below, bestie π«Ά.
π¦ DESCRIPTION π¦
The jstatd command is an RMI server application that monitors for the creation and termination of instrumented Java HotSpot VMs and provides an interface to enable remote monitoring tools, jstat and jps, to attach to JVMs that are running on the local host and collect information about the JVM process. It's giving remote-monitoring main character energy π
The jstatd server requires an RMI registry on the local host. The jstatd server attempts to attach to the RMI registry on the default port, or on the port you specify with the -p port option. If an RMI registry is not found, then one is created within the jstatd application that's bound to the port that's indicated by the -p port option or to the default RMI registry port when the -p port option is omitted. You can stop the creation of an internal RMI registry by specifying the -nr option. Periodt π
π₯ OPTIONS FOR THE JSTATD COMMAND π₯
-nrβ This option does not attempt to create an internal RMI registry within thejstatdprocess when an existing RMI registry isn't found. It's the "no thanks, I'll find my own registry" vibe π.-p portβ This option sets the port number where the RMI registry is expected to be found, or when not found, created if the-nroption isn't specified.-r rmiportβ This option sets the port number to which the RMI connector is bound. If not specified a random available port is used. Surprise port, basically π.-n rminameβ This option sets the name to which the remote RMI object is bound in the RMI registry. The default name isJStatRemoteHost. If multiplejstatdservers are started on the same host, then the name of the exported RMI object for each server can be made unique by specifying this option. However, doing so requires that the unique server name be included in the monitoring client'shostidandvmidstrings. iykyk π§-Joptionβ This option passes a Java option to the JVM, where the option is one of those described on the reference page for the Java application launcher. For example,-J-Xms48msets the startup memory to 48 MB. Seejava.
π SECURITY π
The jstatd server can monitor only JVMs for which it has the appropriate native access permissions. Therefore, the jstatd process must be running with the same user credentials as the target JVMs. Some user credentials, such as the root user in Linux and macOS operating systems, have permission to access the instrumentation exported by any JVM on the system. A jstatd process running with such credentials can monitor any JVM on the system, but introduces additional security concerns. That's a big "be careful" moment, bestie π.
The jstatd server doesn't provide any authentication of remote clients. Therefore, running a jstatd server process exposes the instrumentation export by all JVMs for which the jstatd process has access permissions to any user on the network. This exposure might be undesirable in your environment, and therefore, local security policies should be considered before you start the jstatd process, particularly in production environments or on networks that aren't secure. Not me telling you to check your security policies first π.
For security purposes, the jstatd server uses an RMI ObjectInputFilter to allow only essential classes to be deserialized. Fancy little guardrail β¨.
If your security concerns can't be addressed, then the safest action is to not run the jstatd server and use the jstat and jps tools locally. However, when using jps to get a list of instrumented JVMs, the list will not include any JVMs running in docker containers. That's the trade-off, fr fr π«Ά.
π REMOTE INTERFACE π
The interface exported by the jstatd process is proprietary and guaranteed to change. Users and developers are discouraged from writing to this interface. Like, don't get attached β it's literally guaranteed to change π
.
π EXAMPLES π
The following are examples of the jstatd command. The jstatd scripts automatically start the server in the background. Cute, automatic, lowkey iconic π.
π§ INTERNAL RMI REGISTRY π§
This example shows how to start a jstatd session with an internal RMI registry. This example assumes that no other server is bound to the default RMI registry port (port 1099).
jstatd
β EXTERNAL RMI REGISTRY β
This example starts a jstatd session with an external RMI registry.
rmiregistry&
jstatd
This example starts a jstatd session with an external RMI registry server on port 2020.
jrmiregistry 2020&
jstatd -p 2020
This example starts a jstatd session with an external RMI registry server on port 2020 and JMX connector bound to port 2021.
jrmiregistry 2020&
jstatd -p 2020 -r 2021
This example starts a jstatd session with an external RMI registry on port 2020 that's bound to AlternateJstatdServerName.
rmiregistry 2020&
jstatd -p 2020 -n AlternateJstatdServerName
πΈ STOP THE CREATION OF AN IN-PROCESS RMI REGISTRY πΈ
This example starts a jstatd session that doesn't create an RMI registry when one isn't found. This example assumes an RMI registry is already running. If an RMI registry isn't running, then an error message is displayed. So like, have your registry ready, bestie π.
jstatd -nr
π¦ ENABLE RMI LOGGING π¦
This example starts a jstatd session with RMI logging capabilities enabled. This technique is useful as a troubleshooting aid or for monitoring server activities. Detective mode: activated πβ¨.
jstatd -J-Djava.rmi.server.logCalls=true
π That's the whole page, bestie β brought to you by JDK 27-ea, dated 2026, and filed under JSTATD(1). Slay responsibly π«Άπ
π¦ where this page comes from
- epel 10: java-latest-openjdk-devel 1:27.0.0.0.35-0.0.1.0.ea.el10_3 Β· Apache-1.1 AND Apache-2.0 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-BSD-with-advertising AND GPL-1.0-or-later AND GPL-2.0-only AND LicenseRef-Callaway-GPLv2-with-exceptions AND IJG AND LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-MIT AND MPL-2.0 AND LicenseRef-Callaway-Public-Domain AND W3C AND Zlib AND ISC AND FTL AND LicenseRef-RSA
- epel 10: java-latest-openjdk-devel-fastdebug 1:27.0.0.0.35-0.0.1.0.ea.el10_3 Β· Apache-1.1 AND Apache-2.0 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-BSD-with-advertising AND GPL-1.0-or-later AND GPL-2.0-only AND LicenseRef-Callaway-GPLv2-with-exceptions AND IJG AND LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-MIT AND MPL-2.0 AND LicenseRef-Callaway-Public-Domain AND W3C AND Zlib AND ISC AND FTL AND LicenseRef-RSA
- epel 10: java-latest-openjdk-devel-slowdebug 1:27.0.0.0.35-0.0.1.0.ea.el10_3 Β· Apache-1.1 AND Apache-2.0 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-BSD-with-advertising AND GPL-1.0-or-later AND GPL-2.0-only AND LicenseRef-Callaway-GPLv2-with-exceptions AND IJG AND LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-MIT AND MPL-2.0 AND LicenseRef-Callaway-Public-Domain AND W3C AND Zlib AND ISC AND FTL AND LicenseRef-RSA
- epel 9: java-latest-openjdk-devel 1:27.0.0.0.35-0.0.1.0.ea.el9 Β· Apache-1.1 AND Apache-2.0 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-BSD-with-advertising AND GPL-1.0-or-later AND GPL-2.0-only AND LicenseRef-Callaway-GPLv2-with-exceptions AND IJG AND LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-MIT AND MPL-2.0 AND LicenseRef-Callaway-Public-Domain AND W3C AND Zlib AND ISC AND FTL AND LicenseRef-RSA
- epel 9: java-latest-openjdk-devel-fastdebug 1:27.0.0.0.35-0.0.1.0.ea.el9 Β· Apache-1.1 AND Apache-2.0 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-BSD-with-advertising AND GPL-1.0-or-later AND GPL-2.0-only AND LicenseRef-Callaway-GPLv2-with-exceptions AND IJG AND LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-MIT AND MPL-2.0 AND LicenseRef-Callaway-Public-Domain AND W3C AND Zlib AND ISC AND FTL AND LicenseRef-RSA
- epel 9: java-latest-openjdk-devel-slowdebug 1:27.0.0.0.35-0.0.1.0.ea.el9 Β· Apache-1.1 AND Apache-2.0 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-BSD-with-advertising AND GPL-1.0-or-later AND GPL-2.0-only AND LicenseRef-Callaway-GPLv2-with-exceptions AND IJG AND LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-MIT AND MPL-2.0 AND LicenseRef-Callaway-Public-Domain AND W3C AND Zlib AND ISC AND FTL AND LicenseRef-RSA
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms