IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Class-loader diagnostic data

Class-loader command-line options

There are some extended command-line options that are available

These options are:

-verbose:dynload

Provides detailed information as each class is loaded by the JVM, including:

• The class name and package.
• For class files that were in a .jar file, the name and directory path of the .jar (for bootstrap classes only).
• Details of the size of the class and the time taken to load the class.

The data is written out to stderr. An example of the output follows:

<Loaded java/lang/String from C:\sdk\jre\lib\vm.jar>
<Class size 17258; ROM size 21080; debug size 0>
<Read time 27368 usec; Load time 782 usec; Translate time 927 usec>

-Xfuture

Turns on strict class-file format checks. Use this flag when you are developing new code because stricter checks will become the default in future releases. By default, strict format checks are disabled.

-Xverify[:<option>]

With no parameters, enables the Java™ bytecode verifier, which is the default. Therefore, if used on its own with no parameters, the option has no effect. Optional parameters are:

• all - enable maximum verification
• none - disable the verifier
• remote - enables strict class-loading checks on remotely loaded classes

The verifier is on by default and must be enabled for all production servers. Running with the verifier off, is not a supported configuration. If you encounter problems and the verifier was turned off using -Xverify:none, remove this option and try to reproduce the problem.

Parent: Class-loader diagnostic data

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.