HTTP error and NCSA access log settings
To view this administrative console page, click Application servers > > server name > HTTP error and NCSA access logging .
Use this panel to configure an HTTP error log and NCSA access logs for an HTTP transport channel.
The HTTP error log logs HTTP errors. The level of error logging that occurs is dependent on the value selected for the Error log level field.
The NCSA access log contains a record of all inbound client requests that the HTTP transport channel handles. All of the messages contained in these logs are in NCSA format.
After you have configured the HTTP error log and the NCSA access logs, make sure the Enable NCSA access logging field is selected for the HTTP channels for which you want logging to take place. To view the settings for an HTTP channel, click Servers > Application Servers > server > Web Container Transport Chains > HTTP Inbound Channel.
Configuration tab
- Enable service at server startup
When selected, either an NCSA access log or an HTTP error log, or both will be initialized when the server is started.
- Enable access logging
When selected, a record of inbound client requests that the HTTP transport channel handles is kept in the NCSA access log.
- Access log file path
Directory path and name of the NCSA access log. Standard variable substitutions, such as $(SERVER_LOG_ROOT), can be used when specifying the directory path.
- Access log maximum size
Specifies the maximum size, in megabytes, of the NCSA access log file. When this size is reached, an archive log named logfile_name.1 is created. However, every subsequent time that the original log file overflows this archive file is overwritten with the most current version of the original log file.
- NCSA access log format
Specifies the NCSA format is used when logging client access information. If Common is selected, the log entries contain the requested resource and a few other pieces of information, but does not contain referral, user agent, or cookie information. If Combined in selected, referral, user agent, and or cookie information is included.
- Enable error logging
When selected, HTTP errors that occur while the HTTP channel processes client requests are recorded in the HTTP error log.
- Error log file path
Directory path and name of the HTTP error log. Standard variable substitutions, such as $(SERVER_LOG_ROOT), can be used when specifying the directory path.
- Error log maximum size
Specifies the maximum size, in megabytes, of the HTTP error log file. When this size is reached, an archive log named logfile_name.1 is created. However, every subsequent time that the original log file overflows this archive file is overwritten with the most current version of the original log file.
- Error log level
Specifies the type of error messages that are included in the HTTP error log.
We can select:
- Critical
- Only critical failures that stop the Application Server from functioning properly are logged.
- Error
- Errors in responses to clients are logged. These errors require Application Server administrator intervention if they are caused by server configuration settings.
- Warning
- Information on general errors, such as socket exceptions, that occur while handling client requests are logged. These errors do not typically require Application Server administrator intervention.
- Information
- The status of the various tasks performed while handling client requests is logged.
- Debug
- More verbose task status information is logged. This level of logging is not intended to replace RAS logging for debugging problems, but does provide a steady status report on the progress of individual client requests. If this level of logging is selected, specify a large enough log file size in the Error log maximum size field to contain all of the information that is logged.