Configure the JVM logs

Use the administrative console to configure the JVM logs for an application server.

To log events or information from a running JVM, we can use the administrative console to configure the settings we need for each server. Configuration changes for the JVM logs that are made to a running application server are not applied until the application server is restarted.

This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

1. Start the administrative console

2. Click Troubleshooting > Logs and Trace, then click server > JVM Logs.

3. Select the Configuration tab.

4. Scroll through the panel to display the attributes for the stream to configure.

5. Change the appropriate configuration attributes and click Apply.

6. Save the configuration changes.

Subtopics

• JVM log settings
  Use this page to view and modify the settings for the JVM System.out and System.err logs.

Related tasks

Limiting the growth of JVM log files

Process logs