IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Tracing Java applications and the JVM

Where does the data go?

Trace data can be written to a number of locations.

Trace data can go into:

• Memory buffers that can be dumped or snapped when a problem occurs
• One or more files that are using buffered I/O
• An external agent in real time
• stderr in real time
• Any combination of the other items in this list

• Writing trace data to memory buffers
  Using memory buffers for holding trace data is an efficient method of running trace. The reason is that no file I/O is performed until a problem is detected or until the buffer content is intentionally stored in a file.
• Writing trace data to a file
  You can write trace data to a file continuously as an extension to the in-storage trace, but, instead of one buffer per thread, at least two buffers per thread are allocated, and the data is written to the file before wrapping can occur.
• External tracing
  You can route trace to an agent by using JVMRI TraceRegister.
• Tracing to stderr
  For reduced volume or non-performance-critical tracing, the trace data can be formatted and routed to stderr immediately without buffering.
• Trace combinations
  Most forms of trace can be combined, with the same or different trace data going to different destinations.

Parent: Tracing Java applications and the JVM

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.