Skip Headers
Previous
Previous
 

Available Commands

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

command_line

Prints the command used to start the current JVM instance; for example:

Command Line: -Dapplication.home=C:\jrockit-jdk1.6.0_05 -client -Dsun.java.launcher=SUN_STANDARD com.jrockit.mc.rcp.start.MCMain

datadump_request

Requests a data dump from the JVM Tools Interface (JVMTI). The result of the data dump will appear in the Diagnostic Command Output panel.

dump_codelayout

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.

dump_codelist

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.

dump_codemap

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.

heap_diagnostics

Starts the heap diagnostics utility.

help

Does one of two things:

  • Lists the commands available

  • Generates a description of each command (only if Show help for all commands is selected).

kill_management_server

Stops a default management server from running.

kill_rmp_server

Shuts down the JRockit RMP server.

memleakserver

Depending upon its current state, will either start or stop the memory leak server. You can specify these values:

  • The port to which to bind.

  • The required protocol version.

  • The server toggled on or off.

  • An action to take.

memleakserver

Depending upon its current state, toggles native memory leak detection. You can specify these values:

  • Number of seconds between samples.

  • Number of positive samples to consider.

  • Size, in bytes, that requires full stack statistics.

  • Whether or not to print all known statistics, not just the leaking statistics.

  • Symbols to omit.

oom_diagnostics

Has been deprecated. Use heap_diagnostics instead.

print_class_summary

Prints a list of all loaded classes.

print_codeblocks

Prints the code blocks from the running application.

print_codegenlist

Shows information about the optimizations and code generations queue. To see everything in the list, select Print the content of the list.

print_exceptions

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: -Xverbose:exceptions and the verbosity command to enable or disable the printing of exceptions.

For more information, please refer to the Oracle JRockit JVM Command-Line Reference.

print_memusage

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:

  • Display memory map: Displays the memory map for the application.

  • Display memory by function: Shows memory usage by individual function run during the application.

print_object_summary

Prints detailed information about the objects on the heap. You can specify that the following information be displayed:

  • The names of up to seven classes about which to show points-to information. (name1 though name7).

  • The minimum threshold of total live objects (measured in size) required before a class can be displayed. The percentage should be multiplied by 1000; for example 1.5% would be 1500. The default is 500.

  • The minimum threshold of points-to information required before a class can be displayed. The percentage should be multiplied by 1000; for example 1.5% would be 1500. The default is 500.

  • Whether or not you want to only display the classes that increased since the last listing.

  • Whether or not you want to display sizes in bytes instead of the default kilobytes.

  • A list of all instances of a specified type that points to instances of the type specified by name1.

  • The starting address for an object for which you want to list all instances pointing to that object.

  • The name of an object for which you want to see the total size of all objects it is keeping active.

  • Whether or not to print the 10 largest arrays for the type specified by name1.

  • Whether or not to activate the trend analysis, which will compute the growth for each type in bytes per second and instead of sorting the output by size, sorts it by growth. When trend analysis is active, output will be printed after each garbage collection.

  • Whether or not you want to deactivate trend analysis.

  • The trend analysis period.

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:

  • Include native frames in the stack trace.

  • Print Java stack frames.

  • Print lock information.

  • Include the JVM internal monitors.

  • Print JRockit internal threads.

  • Print java.util.concurrent locks.

  • Print all threads with the same stack trace together (will not print native stack or monitors).

print_utf8pool

Prints all UTF8 string constraints.

print_vm_state

Prints a snapshot of the current VM state.

run_optfile

Loads an optfile with directives to the JVM optimization manager. You can specify an optfile name in the Name of the file edit box.

runfinalization

Calls java.lang.System.runFinalization().

runsystemtempgc

Calls Java and allows you to do a full system garbage collection and force a full compaction for full collections.

sanity

Changes the sanity levels for modules. With this command, you can specify the following:

  • Replace all current sanity levels with those you specify.

  • Specify just certain modules for which you want to change the sanity levels.

set_filename

Sets the name of the file where output from subsequent commands will appear. You can specify the following:

  • A path to the file

  • Whether or not to append new information to the file.

start_management_server

Starts the management server. When you use this command, You can specify the following:

  • The management server's listening port.

  • Whether or not to use a Secure Socket Layer (SSL) connection (default=yes).

  • Whether or not to use authentication (default=yes).

  • Whether or not to enable the autodiscovery service.

  • The user-defined name to broadcast.

  • The port for the SNMP connector.

start_rmp_server

Starts the RMP-based management server. You can also identify the listening port for the management server and enable or disable the autodiscovery service.

timestamp

Prints a current time stamp, which will include uptime for the VM.

verbosity

Changes the verbosity (log) levels. This command works identically to using the command-line option -Xverbose [:<module>[=arg]*]. With this command, you can do th efollowing:

  • Specify the new verbosity levels that will replace the existing levels.

  • Change the verbosity levels for specified modules.

  • Identify the path to the file where verbose information will be appended.

  • Specify whether or not you want to precede verbose printouts with decorations.

versionPrint

Prints Oracle JRockit JVM version information on the report.