WAS v8.5 > Troubleshoot > Work with traceEnable trace at server startup
Use the dmgr console to enable tracing at a server's startup. We can use trace to assist you in monitoring system performance and diagnosing problems. Set thes the initial trace state for a server process. Settings are read at server startup. Some trace service properties can be changed while the server process is running.
As a recommended alternative, we can configure the server to use the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
- Start the dmgr console.
- Click Troubleshooting > Logs and trace in the console navigation tree, then click Server > Diagnostic Trace.
- Click Configuration.
- Do not select the None check box. Trace data is not logged or recorded anywhere. Other handlers (including handlers registered by applications) still have an opportunity to process these traces.
- Select whether to direct trace output to either a file or an in-memory circular buffer.
Different components can produce different amounts of trace output per entry. Naming and security tracing, for example, produces a much higher trace output than web container tracing. Consider the type of data being collected when we configure your memory allocation and output settings.
- If the in-memory circular buffer is selected for the trace output set the size of the buffer, specified in thousands of entries. Maximum number of entries that will be retained in the buffer at any given time.
- If a file is selected for trace output, set the maximum size in megabytes to which the file should be allowed to grow. When the file reaches this size, the existing file will be closed, renamed, and a new file with the original name reopened. The new name of the file will be based upon the original name with a timestamp qualifier added to the name. In addition, specify the number of history files to keep.
- Select the desired format for the generated trace.
- Save the changed configuration.
- To enter a trace string to set the trace specification to the desired state:
- Click Troubleshooting > Logs and trace in the console navigation tree.
- Select a server name.
- Click Change Log Level Details.
- If All Components has been enabled, you might want to turn it off, and then enable specific components.
- Click a component or group name. For more information see the page on log level settings. If the selected server is not running, you will not be able to see individual component in graphic mode.
- Enter a trace string in the trace string box.
- Select Apply, then OK.
- Allow enough time for the nodes to synchronize, and then start the server.
Related
Troubleshoot applications with HPEL
Reference:
Log level settings