Problem Determination Trace is a supplemental trace facility that can provide additional information to help resolve problems that cannot be resolved by examining the standard trace facility. Problem Determination Trace is designed to integrate with the standard trace facility and not replace the standard trace facility.
Problem Determination Trace provides following features:
▪ Good performance:
▪ Log4j2 is supported as trace output.
▪ Mute mode is supported. When you configure Problem Determination Trace in mute mode, trace lines are buffered and output occurs only when critical exceptions happen. This configuration ensures that the runtime performance is not impacted by trace output.
▪ Additional key information is collected:
▪ Session id
▪ Client browser’s version information
▪ Flow state change
▪ Request lifecycle management (RVS) information
When you use traditional trace messages in a production environment, it is hard to identify which user created a message. Also, if a user has several concurrent requests, it is hard to identify which request created the message. The additional key information collected by using Problem Determination Trace helps debug program issues by identifying the user id and user’s client information and state change.
▪ Co-existence with traditional trace facility.
Problem Determination Trace co-exists with the standard trace facility and provides additional features for specific cases of problem determination. The problem determination trace code is separated from the standard trace code, but the messages from both trace programs can be output together.