This chapter describes Java Flight Recorder troubleshooting and security measures.
It includes these sections:
You can collect a significant amount of diagnostic information from Java Flight Recorder by starting the JVM with the command-line option -XX:FlightRecorderOptions=loglevel=debug or -XX:FlightRecorderOptions=loglevel=trace. For more information about the -XX:FlightRecorderOptions option, see the Java Command Line Reference at
http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/java.html (Solaris, Linux)
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/java.html (Windows)
Java Flight Recorder is intended only for diagnostic purposes. The recording file can potentially contain confidential information such as Java command-line options and environmental variable settings. Use extreme care when you store or transfer the recording files as you would do with diagnostic core files or heap dumps.
You can only start a recording by using one of the following means: the command line, diagnostic commands, or Java Mission Control. These methods provide security as described in Table 5-1:
Table 5-1 Security Permissions
| Method | Security |
|---|---|
|
Command line |
Anyone with access to the command line of the Java process must be trusted. |
|
Diagnostic Command |
Only the owner of the Java process can use jcmd to control the process. |
|
Java Mission Control Client |
Java Mission Control Client uses JMX to access the JVM. . |
