WAS v8.5 > Troubleshoot > Use Cross Component Trace

XCT

XCT annotates the logs so that log entries related to a request that is serviced by more than one thread, process, or even server are identified as belonging to the same unit of work.


Overview

New feature:

XCT helps identify the root cause of problems across components, which provides the following benefits:


Administration of XCT

XCT is a capability built into the WAS log and trace framework. When enabled, XCT annotates the logs so that log entries related to a request that is serviced by more than one thread, process, or even server are identified as belonging to the same unit of work. Applications built using distributed architectures, such as Service Oriented Architecture, will benefit from XCT, since XCT helps facilitate problem determination across multiple services on different systems.

XCT different modes:

XCT request IDs:

The following is an example of a log record with an XCT request ID in the log file (shown rendered in advanced format):

[3/18/11 14:50:17:391 EDT] 00000018 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= 
 thread=[WebContainer : 1] requestID=BJrcVPo+Yk4-AAAAAAA8zAA hello world

Note the request ID is shown previously on a separate line, but in the log files it is actually on the same line as the rest of the log record header.

XCT log records:

XCT tools:

XCT configuration:

We can configure XCT using wsadmin.sh.


Related


Configure XCT with wsadmin scripting


+

Search Tips   |   Advanced Search