This chapter describes how to change the way Java Mission Control logs errors and warnings.
Note:
Java Mission Control requires a commercial license for use in production. To learn more about commercial features and how to enable them please visithttp://www.oracle.com/technetwork/java/javaseproducts/.By default, the JMC client uses the logging.properties file located in the com.jrockit.mc.rcp.application package (Java Archive or JAR file) to control the way that logging is performed. For example, if you have a commercial license of the JDK installed in JAVA_HOME, the location of this JAR file should be JAVA_HOME/lib/missioncontrol/plugins.
In JMC 5.5, you can use a system property to specify the logging configuration file. Either start JMC with jmc -vmargs -Djava.util.logging.config.file=<the logging file to use>, or update the -vmargs section of the jmc.ini file, adding a line that says -Djava.util.logging.config.file=<the logging file to use>.
You can also switch to debug logging by simply starting JMC with jmc -debug.