WAS v8.5 > Troubleshoot

Configure Java logging

Java logging provides a standard logging API for the applications.

Using the dmgr console, we can:

• Enable or disable a particular log, specify where log files are stored and how many log files are kept.
• Specify the level of detail in a log, and specify a format for log output.
• Set a log level for each logger.

We can change the log configuration statically or dynamically. Static configuration changes affect applications when we start or restart the application server. Dynamic or run time configuration changes apply immediately.

When you change the level of a logger, the change is propagated to the children of the logger, which recursively propagates the change to their children, as necessary.

1. Set the output properties for a log:
   1. In the navigation pane, click...
      Troubleshooting | Log and trace | server | system log

   2. To make a static change to the system log configuration, click the Configuration tab. To change the configuration dynamically, click the Runtime tab.

   3. Change the properties for the selected log according to your needs.

   4. Click Apply.

   5. Click OK.

2. Set the logging levels for the logs:
   1. In the navigation pane, click...
      Servers | Server Types | WebSphere application servers | servername | Troubleshooting | Logs and Trace | Change Log Detail levels | [Configuration|Runtime]

   2. Select a component, package, or group to set a logging level.

   3. [HPEL] Select whether to disable the logging and tracing of potentially sensitive data.

   4. Click Apply.

   5. Click OK.

3. To have static configuration changes take effect, stop then restart the application server.

Subtopics

• Log streams and expected output
• Change the message IDs used in log files
• Log streams and expected output
• Log level settings
• Change the message IDs used in log files
• HTTP error, FRCA, and NCSA access log settings

+

Search Tips   |   Advanced Search