WAS v8.5 > Troubleshoot

Use Cross Component Trace (XCT) to troubleshoot applications

Use XCT to augment log and trace files with correlation information that clarifies which threads, and which application server processes, participated in the handling of each request.

1. Enable XCT...
   Troubleshooting | Logs and trace server | Change log detail levels | [Configuration|Runtime] | Enable log and trace correlation

   Options...

   • Include request IDs in log and trace records and correlation log records
   • Include request IDs in log and trace records
   • Create correlation log records
   • Capture data snapshots

   Request IDs are only recorded when using HPEL log and trace mode.

   Data snapshots include message requests and responses handled by the SIBus, and are written to...

   $SERVER_LOG_ROOT/snapdata

   The application server does not automatically clean files from this directory. Manually delete periodically. Data snapshots store entire request and response contents and may include sensitive information. This option might not be appropriate for use in production environments.

   Enabling XCT has a performance impact. Use in test and development environments. Capturing data snapshots means an addditional performance hit.

2. Use XCT request ID information to track requests.

   1. Enable High Performance Extensible Logging (HPEL) log and trace mode.

      Basic mode log and trace does not store request IDs.

   2. Enable XCT...
      Troubleshooting | Logs and trace server | Change log detail levels | [Configuration|Runtime] | Enable log and trace correlation

   3. To see request ID information in the logs...
      ./logViewer.sh -minLevel WARNING -format advanced

   4. When we have found log entries that are of interest to you, note the request ID associated with those entries.

   5. Filter logs by request ID using LogViewer withe the request IDs noted in the previous step...
      ./logViewer.sh -includeExtensions requestID=<requestID>

3. Use XCT correlation log records to determine the hierarchy of call chains.

   1. Enable XCT
      Troubleshooting | Logs and trace server | Change log detail levels | [Configuration|Runtime] | Enable log and trace correlation

      ...selecting...

      Include request IDs in log and trace records and correlation log records

   2. If we are using HPEL, convert logs to text with

      For example...

      ./logViewer.sh -outLog myLog.txt

   3. To see the hierarchy of request call chains, use the WebSphere Cross Component Trace Logviewer tool, available with the IBM Support Assistant, to load log and trace files

Related

1. XCT
   
2. Configure XCT with wsadmin scripting
   
3. Change from basic mode to HPEL logging and tracing
4. Use IBM Support Assistant
5. LogViewer command-line tool

+

Search Tips   |   Advanced Search