Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Troubleshoot ActivitySessions
Troubleshoot ActivitySessions
Use this overview task to help resolve a problem that you think is related to the ActivitySession service.
New feature: This topic references one or more of the application server log files. Beginning in WAS v8.0 you 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 or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.newfeat
To identify and resolve ActivitySession-related problems, you can use the standard WAS RAS facilities. If you encounter a problem that you think might be related to ActivitySessions, complete the following stages:
Procedure
- 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.
- 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.
The ActivitySession service
Use HPEL to troubleshoot applications
Implement WebSphere enterprise applications that use ActivitySessions