IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Using dump agents
Removing dump agents
You can remove all default dump agents and any preceding dump options by using -Xdump:none.
The following syntax diagram shows you how you can use the none option:
-Xdump command-line syntax: the none option >>--Xdump:------------------------------------------------------> .-,---------------------------. | .-+-----------. | V V | | >--+-none---:---+-events=-----<event>---+-+-+----------------+->< | +-exec=<command>----------+ | | +-file=<filename>---------+ | | +-filter=<filter>---------+ | | +-opts=<options>----------+ | | +-priority=<0-999>--------+ | | +-range=<ranges>----------+ | | '-request=<requests>------' | | .-,---------------------------. | | .-+-------. | .-+-----------. | | | V | V V | | | '---<agent>-+-:none---:---+-events=-----<event>---+-+-+---' +-exec=<command>----------+ +-file=<filename>---------+ +-filter=<filter>---------+ +-opts=<options>----------+ +-priority=<0-999>--------+ +-range=<ranges>----------+ '-request=<requests>------'
Use this option so that you can subsequently specify a completely new dump configuration.
You can also remove dump agents of a particular type. Here are some examples:
To turn off all Heapdumps (including default agents) but leave Javadump enabled, use the following option:
-Xdump:java+heap:events=vmstop -Xdump:heap:none
To turn off all dump agents for corruptcache events:
-Xdump:none:events=corruptcache
To turn off just system dumps for corruptcache events:
-Xdump:system:none:events=corruptcache
To turn off all dumps when java/lang/OutOfMemory error is thrown:
-Xdump:none:events=systhrow,filter=java/lang/OutOfMemoryError
To turn off just system dumps when java/lang/OutOfMemory error is thrown:
-Xdump:system:none:events=systhrow,filter=java/lang/OutOfMemoryError
If you remove all dump agents using -Xdump:none with no further -Xdump options, the JVM still provides these basic diagnostic outputs:
- If a user signal (
kill -QUIT) is sent to the JVM, a brief listing of the Java™ threads including their stacks, status, and monitor information is written to stderr.
- If a crash occurs, information about the location of the crash, JVM options, and native and Java stack traces are written to stderr. A system dump is also written to the user's home directory.
Tip: Removing dump agents and specifying a new dump configuration can require a long set of command-line options. To reuse command-line options, save the new dump configuration in a file and use the -Xoptionsfile option. See Specifying command-line options for more information on using a command-line options file.
Parent: Using dump agents
Error 404 - Not Found 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.