Table B-1 lists the -D options that enable you to access remote JRockit JVM instances in Oracle JRockit Mission Control using a Java Management Extensions (JMX) connector.
Note:
Unless explicitly stated, the options listed in Table B-1 are also available in thecom.sun.management
namespace.
Oracle recommends that you use the equivalent -Xmanagement command-line options for -D options (if available).
Table B-1 JMX Agent-Related -D Options in R28
-D Option | Description | Default Value |
---|---|---|
See -Xmanagement. |
When you set this option to |
|
See -Xmanagement:port |
7091 |
|
See -Xmanagement:interface |
null |
|
See -Xmanagement:rmiserver_port |
None |
|
See -Xmanagement:registry_ssl |
false |
|
-Dcom.oracle.management.jmxremote.ssl |
See -Xmanagement:ssl |
true |
-Dcom.oracle.management.jmxremote.ssl.enabled.protocols |
A comma-delimited list of SSL or TLS Protocol versions to be enabled. This option is used with com.oracle.management.jmxremote.ssl. |
Default SSL or TLS Protocol |
-Dcom.oracle.management.jmxremote.ssl.enabled.cipher.suites |
A comma-delimited list of SSL or TLS cipher suites to be enabled. This option is used with com.oracle.management.jmxremote.ssl. |
Default SSL or TLS cipher suites |
-Dcom.oracle.management.jmxremote.ssl.need.client.auth |
When this property is set to |
false |
See -Xmanagement:authenticate |
|
|
-Dcom.oracle.management.jmxremote.password.file |
Specifies the location for the password file. If the com.oracle.management.jmxremote.authenticate property is false then this property and the password and access files are ignored. Otherwise, the password file must exist and it should be in the valid format. If the password file is empty or does not exist, you cannot access the remote JVM. |
|
-Dcom.oracle.management.jmxremote.access.file |
Specifies the location for the access file. If the com.oracle.management.jmxremote.authenticate property is |
|
Specifies the name of a Java Authentication and Authorization Service (JAAS) login configuration entry to use when the JMX agent authenticates users. When using this property to override the default login configuration, the named configuration entry must be in a file that is loaded by JAAS. In addition, the login modules specified in the configuration should use the name and password callbacks to acquire the user credentials. For more information, see the API documentation for javax.security.auth.callback.NameCallback and javax.security.auth.callback.PasswordCallback. |
Default login configuration is a file-based password authentication. |
|
See -Xmanagement:config.file |
|
|
-Dcom.oracle.management.snmp.port |
Enables the SNMP agent on a specified port. |
None |
-Dcom.oracle.management.snmp.trap |
Specifies the remote port to which the SNMP agent sends traps. |
162 |
-Dcom.oracle.management.snmp.acl |
Enables Access Control List for the SNMP agent. |
true |
-Dcom.oracle.management.snmp.acl.file |
Specifies the location of valid ACL file. Once the SNMP agent is started, you cannot modify the ACL file. |
|
-Dcom.oracle.management.snmp.interface |
Specifies the local host InetAddress. The SNMP agent will then bind to the specified InetAddress. This is used when you have multihome hosts and you want the port to listen only to a specific subnet. This property is optional. |
None |
See -Xmanagement:autodiscovery |
false |
|
-Dcom.oracle.management.autodiscovery.period |
Specifies the time interval between the broadcast messages during autodicovery in milliseconds. |
5000 milliseconds |
-Dcom.oracle.management.autodiscovery.ttl |
Time-to-live for autodiscovery packets. |
1 |
-Dcom.oracle.management.autodiscovery.address |
Multicast address to send autodiscovery packets. |
232.192.1.212 |
-Dcom.oracle.management.autodiscovery.port |
Multicast port to send autodiscovery packets |
7095 |
-Dcom.oracle.management.autodiscovery.name |
Broadcast name of the JVM |
|
-Dcom.oracle.management.autodiscovery.property.prefix |
Copies all system properties starting with a specified prefix to the autodiscovery packets and make them available to remote agent. |