![]() Previous |
You can run the commands listed in Table 1 from the Diagnostic Commands tab.
Diagnostic Commands for Use with the Diagnostic Commands Tab
| Command | Description |
|---|---|
|
|
Prints the command used to start the current JVM instance; for example:
|
|
|
Requests a data dump from the JVM Tools Interface (JVMTI). The result of the data dump will appear in the Diagnostic Command Output panel. |
|
|
Dumps the code memory layout as an XML file. If there is a result, the layout will print either to the Diagnostic Command Output panel or to an output file, which you can specify by entering a file name in the Name of file to store (optional) field. |
|
|
Creates a simple code listing file for generated Java methods. If there is a result, the list will print either to the Diagnostic Command Output panel or to an output file, which you can specify by entering a file name in the Name of file to store (optional) field. |
|
|
Creates a map file for the Java methods generated. The map file format will be based on the specific compiler. If there is a result, the map will print either to the Diagnostic Command Output panel or to an output file, which you can specify by entering a file name in the Name of file to store (optional) field. |
|
|
Starts the heap diagnostics utility. |
|
|
Does one of two things:
|
|
|
Stops a default management server from running. |
|
|
Shuts down the JRockit RMP server. |
|
|
Depending upon its current state, will either start or stop the memory leak server. You can specify these values:
|
|
|
Depending upon its current state, toggles native memory leak detection. You can specify these values:
|
|
|
Has been deprecated. Use |
|
|
Prints a list of all loaded classes. |
|
|
Prints the code blocks from the running application. |
|
|
Shows information about the optimizations and code generations queue. To see everything in the list, select Print the content of the list. |
|
|
Prints all exceptions thrown inthe Oracle JRockit JVM. This command is deprecated. The preferred way of displaying exceptions is to use the exceptions logging module: For more information, please refer to the Oracle JRockit JVM Command-Line Reference. |
|
|
Prints detailed information on how much memory is used by different JVM subsystems. You can specify what to print by selecting one of the available options:
|
|
|
Prints detailed information about the objects on the heap. You can specify that the following information be displayed:
|
|
print_properties |
Prints all the Java and VM properties. |
|
print_threads |
Prints all threads with stack traces. You can set whether or not to do the following:
|
|
print_utf8pool |
Prints all UTF8 string constraints. |
|
print_vm_state |
Prints a snapshot of the current VM state. |
|
run_optfile |
Loads an |
|
runfinalization |
Calls |
|
|
Calls Java and allows you to do a full system garbage collection and force a full compaction for full collections. |
|
|
Changes the sanity levels for modules. With this command, you can specify the following:
|
|
|
Sets the name of the file where output from subsequent commands will appear. You can specify the following:
|
|
|
Starts the management server. When you use this command, You can specify the following:
|
|
|
Starts the RMP-based management server. You can also identify the listening port for the management server and enable or disable the autodiscovery service. |
|
|
Prints a current time stamp, which will include uptime for the VM. |
|
|
Changes the verbosity (log) levels. This command works identically to using the command-line option
|
|
|
Prints Oracle JRockit JVM version information on the report. |