IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Tracing Java applications and the JVM > Controlling the trace
Detailed descriptions of trace options
The options are processed in the sequence in which they are described here.
-Xtrace command-line option syntax >>--Xtrace:----------------------------------------------------->    .-,--------------------------------------------------.      V |   >----+-properties[=<filename>]------------------------+-+------><    +-buffers=<size>[,-+-dynamic---+-]---------------+       | '-nodynamic-' |       | .-,--------------------------. |       | V | |       +-+-minimal---+-=---<tracepoint_specification>-+-+       | +-maximal---+ |       | +-count-----+ |       | +-print-----+ |       | +-iprint----+ |       | +-exception-+ |       | +-external--+ |       | '-none------' |       | .-,----------------------. |       | V | |       +-methods=---<method_specification>-+------------+       +-output=<filename>[,<size>[,<generations>]]-----+       +-exception.output=<filename>[,<size>]-----------+       +-resume-----------------------------------------+       +-resumecount=<count>----------------------------+       +-sleeptime=nnn|aaams|bbbs-----------------------+       +-stackdepth=<n>---------------------------------+       +-suspend----------------------------------------+       +-suspendcount=<count>---------------------------+       | .-,--------. |       | V | |       +-trigger=---<clause>-+--------------------------+       '-what-------------------------------------------'   Â
- properties[=<filename>]
You can use properties files to control trace. A properties file saves typing and, over time, causes a library of these files to be created. Each file is tailored to solving problems in a particular area.- buffers=nnnk|nnnm[,dynamic|nodynamic]
You can modify the size of the buffers to change how much diagnostics output is provided in a snap dump. This buffer is allocated for each thread that makes trace entries.- Options that control tracepoint activation
These options control which individual tracepoints are activated at run time and the implicit destination of the trace data.- methods=<method_specification>[,<method_specification>]
Using method trace provides a complete (and potentially large) diagnosis of code paths inside your application and the system classes. Use wild cards and filtering to control method trace so that you can focus on the sections of code that interest you.- output=<filename>[,sizem[,<generations>]]
Use the output option to send trace data to <filename>. If the file does not already exist, it is created automatically. If it does already exist, it is overwritten.- exception.output=<filename>[,nnnm]
Use the exception option to redirect exception trace data to <filename>.- resume
Resumes tracing globally.- resumecount=<count>
This trace option determines whether tracing is enabled for each thread.- sleeptime=nnn|aaams|bbbs
Specify how long the sleep lasts when using the sleep trigger action.- stackdepth=<n>
Used to limit the amount of stack frame information collected.- suspend
Suspends tracing globally (for all threads and all forms of tracing) but leaves tracepoints activated.- suspendcount=<count>
This trace option determines whether tracing is enabled for each thread.- trigger=<clause>[,<clause>][,<clause>]...
This trace option determines when various triggered trace actions occur. Supported actions include turning tracing on and off for all threads, turning tracing on or off for the current thread, or producing various dumps.- what
This trace option shows the current trace settings.
Parent: Controlling the trace
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.