InfoCenter Home > 8.3: LogsWebSphere Application Server provides many error logs to help you diagnose run-time problems. This section describes these error logs telling you where to find and how to format the files. The logs are:
The tools required to process some of these logs (as well as some of the trace logs) are described in Using Internal Tools. You can also refer to Problem determination hints and tips for additional tips on the use and processing of some of these error logs. If you need to report a problem to IBM, you might need to gather some of these error logs and send them to IBM for diagnosis; for more information, refer to How to report a problem to IBM. View the following graphic for a description of the log and trace points in
WebSphere Application Server:
![]()
InfoCenter Home > Activity log for problem determinationThe activity log captures events that show a history of WebSphere Application Server's activities. Some of the entries in the log are informational, while others report on system exceptions, such as returned CORBA exceptions. When you encounter WebSphere Application Server run-time errors, you will often find it useful to use Log Analyzer to read the activity log and try to diagnose the problem yourself. When you need assistance from IBM to help you diagnose problems, you will be asked to provide the formatted activity log output to IBM. Location of the activity logThere is one activity log for each host machine. The activity.log file resides in the logs directory of where the product is installed. All application servers, including the administrative server, write error records to this file. The activity.log file is a binary file and cannot be viewed with an ascii editor. You can view the activity.log file in one of two ways:How to view the activity.log file with Log Analyzer
Changing activity.log file sizeIn the course of using Log Analyzer, you might have to set the maximum activity.log file size. The activity.log file grows to a predetermined size and then wraps. The default size is 1MB. Follow these steps to change the log size: The size change will take effect at the next server startup. See other related tasks, including changing the port of the logging service, diagnosing port conflicts and confirming the creation of the activity.log file in the Log Analyzer section. InfoCenter Home >8: Problem determination > 8.3: Logs <- you are here stderr and stdout logs for problem determinationThe stderr and stdout logs capture events presented through two of the three standard I/O streams, or: In WebSphere Application Server, the stdout and stderr logs are created for: The application server stderr and stdout logs contain application server communication. Output from System.err.println and System.out.println statements in the servlet code also appear in the application server stdout and stderr logs.
InfoCenter Home > Out-of-process(oop) logs for problem determinationThere are two types of out-of-process logs: those created for administrative servers and those created for application servers. These logs contain error and informational messages generated from the native code portion of the out-of-process engine. This information reflects server startup and server status change requests (start/stop/restart). The default log file mask setting for the oop logs is error. If these logs have a file length of zero, no error messages were generated during the server status change requests. To change the default log file file mask setting:The oop log files are now dated so the file format is consistent with that of the HTTP Server trace logs. For example, an administrative server oop log file name is: adminserver_native.log.was.oop.Thu_May_26_23.26.20.2000
InfoCenter Home >
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|