JDK9-JSE性能监控与管理指南-67.pdf

需积分: 5 174 浏览量更新于2023-11-23 收藏 1.25MB PDF 举报

JDK9-JSE-Monitoring and Management Guide-67.pdf 是Java平台标准版的监控和管理指南，是2017年9月发布的第9版。该文件受版权法保护，包括软件和相关文档，受许可协议限制使用和披露。除非在许可协议中明确允许或法律允许的情况下，禁止使用、复制、翻译、广播、修改、许可、传输、分发、展览、执行、发布或显示任何部分。反向工程、反汇编或解编软件也是被禁止的，除非法律规定要求进行互操作性操作。

Monitoring and Management Using JMX

Technology

The Java virtual machine (Java VM) has built-in instrumentation that enables you to

monitor and manage it using the Java Management Extensions (JMX) technology.

These built-in management utilities are often referred to as out-of-the-box

management tools for the Java VM. You can also monitor any appropriately

instrumented applications using the JMX API.

Setting System Properties

To enable and configure the ready-to-use JMX agent so that it can monitor and

manage the Java VM, you must set certain system properties when you start the Java

VM. You set a system property on the command line as follows:

java -Dproperty=value ...

You can set any number of system properties in this way. If you do not specify a value

for a management property, then the property is set with its default value. See

Table 2-1 for the full set of ready-to-use management properties. You can also set

system properties in a configuration file, as described in the Ready-to-Use Monitoring

and Management Properties section.

Note:

To run the Java VM from the command line, you must add

JRE_HOME/bin

your path, where

JRE_HOME

is the directory containing the Java Runtime

Environment (JRE) implementation. Alternatively, you can enter the full path

when you enter the command.

The syntax and the full set of command-line options supported by the Java HotSpot

VMs are described in the Java application launcher section of Java Platform, Standard

Edition Tools Reference.

Enabling the Ready-to-Use Management

To monitor a Java platform using the JMX API, you must do the following:

1. Enable the JMX agent (another name for the platform MBean server) when you

start the Java VM. You can enable the JMX agent for:

• Local monitoring, for a client management application running on the local

system.

• Remote monitoring, for a client management application running on a remote

system.

2-1

2. Monitor the Java VM with a tool that complies with the JMX specification, such as

JConsole. See Using JConsole.

Local Monitoring and Management

Earlier while starting the Java VM or Java application, you set the following property to

allow the JMX client access to a local Java VM:

com.sun.management.jmxremote

Setting this property registered the Java VM platform's MBeans and published the

remote method invocation (RMI) connector through a private interface. This setting

allows JMX client applications to monitor a local Java platform, that is, a Java VM

running on the same machine as the JMX client.

In the current Java SE platform, it is no longer necessary to set this system property.

Any application that is started on the current Java SE platform supports the Attach

API, and will automatically be made available for local monitoring and management

when needed.

For example, previously, to enable the JMX agent for the Java SE sample application

Notepad

, you would run the following commands:

% cd JDK_HOME/demo/jfc/Notepad

% java -Dcom.sun.management.jmxremote -jar Notepad.jar

In the preceding command,

JDK_HOME

is the directory in which the Java Development

Kit (JDK) is installed. In the current Java SE platform, you have to run the following

command to start

Notepad

% java -jar Notepad.jar

After

Notepad

has been started, a JMX client using the Attach API can then enable the

out-of-the-box management agent to monitor and manage the

Notepad

application.

Note:

On Windows platforms, for security reasons, local monitoring and

management is supported only if your default temporary directory is on a file

system that allows the setting of permissions on files and directories (for

example, on a New Technology File System (NTFS) file system). It is not

supported on a File Allocation Table (FAT) file system, which provides

insufficient access controls.

Local Monitoring and Management Using JConsole

Local monitoring with JConsole is useful for development and creating prototypes.

Using JConsole locally is not recommended for production environments, because

JConsole itself consumes significant system resources. Rather, you should use

JConsole on a remote system to isolate it from the platform being monitored.

However, if you do wish to perform local monitoring using JConsole, then you start the

tool by entering

jconsole

in a command shell. When you start

jconsole

without any

arguments, it will automatically detect all local Java applications, and display a dialog

box that enables you to select the application that you want to monitor. Both JConsole

Chapter 2

Enabling the Ready-to-Use Management

2-2

and the application must by executed by the same user, because the monitoring and

management system uses the operating system's file permissions.

Note:

To run JConsole from the command line, you must add

JDK_HOME/bin

to your

path. Alternatively, you can enter the full path when you enter the command.

See Using JConsole.

Remote Monitoring and Management

By default, the remote stubs for locally created remote objects that are sent to client

contains the IP address of the local host in

dotted-quad

format. For remote stubs to be

associated with a specific interface address, the

java.rmi.server.hostname

system

property must be set to IP address of that interface.

To enable monitoring and management from remote systems, you must set the

following system property when you start the Java VM:

com.sun.management.jmxremote.port=portNum

Where,

portNum

is the port number to enable JMX RMI connections. Ensure that you

specify an unused port number. In addition to publishing an RMI connector for local

access, setting this property publishes an additional RMI connector in a private read-

only registry at the specified port using the name,

jmxrmi

. The port number to which

the RMI connector will be bound using the system property:

com.sun.management.jmxremote.rmi.port

Ensure to use an unused port number.

Note:

You must set the prior system property in addition to any properties that you

might set for security.

Remote monitoring and management requires security to ensure that unauthorized

persons cannot control or monitor your application. Password authentication over the

Secure Sockets Layer (SSL) and Transport Layer Security (TLS) is enabled by default.

You can disable password authentication and SSL separately.

Note:

For production systems, use both SSL client certificates to authenticate the

client host and password authentication for user management. See Using SSL

and Using LDAP Authentication.

The Java platform supports pluggable login modules for authentication. You can

plug in any login module depending on the authentication infrastructure in your

organization. Using LDAP Authentication describes how to plug in the

Chapter 2

Enabling the Ready-to-Use Management

2-3

剩余66页未读，继续阅读

weixin_40191861_zj

粉丝: 85
资源: 1万+

JDK9-JSE性能监控与管理指南-67.pdf

JDK10-JSE ,Installation Guide-57.pdf

JDK10-JSE ,Monitoring and Management Guide-68.pdf

JDK9-JSE-Nashorn User's Guide-32.pdf

bcprov-jdk14-145.jar

jdk-8.0.302.8-hotspot和jdk1.8区别

bcprov-jdk16-1.46.jar has unsigned entries - org/bouncycastle/LICENSE.class

3、安装和配置JDK rpm -qa|grep openjdk packages中jdk-8u211-linux-x64.tar.gz cd /opt/packages tar -zxvf jdk-8u211-linux-x64.tar.gz -C /opt/programs vi /etc/profile export JAVA_HOME=/opt/programs/jdk1.8.0_211 export PATH=$PATH:$JAVA_HOME/bin source /etc/profile java -version写注释

aspose-words-21.6.0-jdk17.jar下载

lrwxrwxrwx. 1 root root 26 6月 8 01:35 jdk-11.0.19 -> /export/server/jdk-11.0.19 lrwxrwxrwx. 1 root root 47 6月 8 01:06 jdk-11.0.19_linux-x64_bin.tar.gz -> /export/server/jdk-11.0.19_linux-x64_bin.tar.gz

最新资源