Application server log files
When starting and stopping an application server, a number of log files are generated. After starting or stopping an application server check the log files to ensure that both the application server and the application that run inside the application server started or stopped successfully.
The application server log files are...
- WC_PROFILE/logs/server1
- WCDE_INSTALL/wasprofile/logs/server1
The following log files should be examined after starting or stopping an application server:
- stopServer.log
- This log file contains messages generated when the application server was stopping. The application server stopped successfully if this log file contains the text, Server server_name stop completed, where server_name is the name of the application server that was stopped.
- SystemErr.log
- This log file contains Java exceptions and stack traces. These exceptions are caught by enterprise applications and their associated application servers.
An empty SystemErr.log file does not necessarily indicate success since not all error messages generated by an application are considered to be error messages by the operating system. You must also examine the contents of the SystemOut.log file.
- SystemOut.log
- This log file contains messages generated when the applications running inside the application server are being started or stopped. This log file will not contain error messages - such messages will appear in the SystemErr.log file. However, this log file will contain error messages that the operating system does not see as error messages.
Both this log file and the SystemErr.log file should be checked after starting an application server to confirm that the applications inside the application server being started have also started successfully.
- trace.log
- The log file contains the components trace messages while the service is running, if the trace is enabled in the server.
When working with IBM to debug request processing problems, there might be occasions where low-level tracing components must be enabled to capture details for how the request is processed. These low-level Application server trace components do not have knowledge of the request intent or the potential data within. Therefore, when enabled, it is possible that these tracing components might potentially include sensitive information, in plain text, in the trace file.
IBM recommends whenever possible to not enable these types of tracing components on a production system and attempt to simulate the problem on a quality assurance environment to capture the appropriate information. However, when this is not possible and the tracing components might have to be enabled on a production system, it is recommend to take the necessary precautions when handling the trace files. Before sending the trace, any sensitive data contained in the trace should be removed when a third party is using them for diagnosing the problem. Further, when the trace is no longer required, the files should be removed using a military-grade data wiping process. Once the problem has been determined and the tracing component is no longer required, those tracing components should immediately be disabled.
Other log files might appear in the directory but they are not related to the starting and stopping of an application server. For more information about the log files that are displayed in the log files directory, go to the WebSphere Application Server V7 and search for message logs.