HTTP error and NCSA access log settings
Use this page to configure an HTTP error log and National Center for Supercomputing Applications (NCSA) access logs for an HTTP transport channel. The HTTP error log contains HTTP errors. The level of error logging that occurs is dependent on the value that is selected for the Error log level field.
To view this console page, click...
Application servers | server name | HTTP error and NCSA access loggingThe NCSA access log contains a record of all inbound client requests that the HTTP transport channel handles. All of the messages that are contained in these logs are in NCSA format.
After you configure the HTTP error log and the NCSA access logs, make sure that the Enable NCSA access logging field is selected for the HTTP channels for which you want logging to occur. 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 are initialized when the server starts.
- 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
Indicates the 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
Indicates the maximum size, in megabytes, of the NCSA access log file. When this size is reached, the logfile_name.1 archive log is created. However, every time that the original log file overflows this archive file, the file is overwritten with the most current version of the original log file.
- NCSA access log format
Indicates that 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 is 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
Indicates the directory path and the 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
Indicates the maximum size, in megabytes, of the HTTP error log file. When this size is reached, the logfile_name.1 archive log is created. However, every time that the original log file overflows this archive file, this file is overwritten with the most current version of the original log file.
- Error log level
Indicates the type of error messages that are included in the HTTP error log. You can select:
- Critical
- Only critical failures that stop the Application Server from functioning properly are logged.
- Error
- The errors that occur in response to clients are logged. These errors require Application Server administrator intervention if they result from 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 that are 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.
Related tasks
Configure Java logging using the console