Troubleshooting ActivitySessions

Use this overview task to help resolve a problem that you think is related to the ActivitySession service.

This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

To identify and resolve ActivitySession-related problems, we can use the standard WebSphere Application Server RAS facilities. If we encounter a problem that you think might be related to ActivitySessions, complete the following stages:

1. Check for ActivitySession messages in the admin console. The ActivitySession service produces diagnostic messages prefixed by "WACS". The error message indicates the nature of the problem and provides some detail. The associated message information provides an explanation and any user actions to resolve the problem.

2. Check for ActivitySession messages. The ActivitySession service produces diagnostic messages prefixed by "WACS". The error message indicates the nature of the problem and provides some detail. The associated message information provides an explanation and any user actions to resolve the problem. Activity log messages produced by the ActivitySession service are accompanied by Log and Trace Analyzer descriptions.

   Check in the application server's SystemOut log at was_home\logs\server\SystemOut for error messages with the prefix WACS. If needed, check other messages, which should provide extra details about the problem.

   Check in the SYSPRINT or SYSOUT log for error messages with the prefix WACS. If needed, check other messages, which should provide extra details about the problem.

Related concepts

The ActivitySession service

Related tasks

Use High Performance Extensible Logging to troubleshoot applications