HTTP error and NCSA access log settings

Use this page to configure an HTTP error log and National Center for Supercomputing Applications (NCSA) access log 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 administrative console page, click Application servers > server name > HTTP error and NCSA access logging.

[z/OS] On a z/OS platform, HTTP error and NCSA access logging is done in the controller.

The 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 a NCSA access log are in NCSA format.

The HTTP error log contains a record of HTTP processing errors that occur. The level of error logging that occurs is dependent on the value that is selected for the Error log level field.

Configuring and enabling the logging is a two step process. After you use this page to configure the logging, you must explicitly enable each type of logging for the appropriate HTTP channels. To view the settings page for an HTTP channels, click Servers > Application Servers > server > Web container transport chains > Chain > HTTP inbound channel.

NCSA access logging

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

Specifies 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.

[z/OS] On the z/OS platform, you should use a server-specific variable, such as $(SERVER_LOG_ROOT), to prevent log name collisions.

Access log maximum size

Specifies the maximum size, in megabytes, of the NCSA access log. When the content of the NCSA access log reaches the specified maximum size limit, a [Updated in August 2011] <logname>.<timestamp>.log archive file [Updated in August 2011]

aug2011
is created. The current content of the NCSA access log is then copied to this archive log.

[Updated in August 2011] An example of a file name for this archive log follows::
ncsa_access_11_08_20_16.11.04.log
[Updated in August 2011]
aug2011

The next time the content in the NCSA access log reaches the specified maximum log size, the content of the NCSA access log is again copied to the [Updated in August 2011] <logname>.<timestamp>.log archive file [Updated in August 2011]

aug2011
. The copy process overwrites the current content of the archive log with the most current content of the NCSA access log.

NCSA access log format

Specifies 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.

Error logging

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

Specifies 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.

[z/OS] On the z/OS platform, you should use a server-specific variable, such as $(SERVER_LOG_ROOT), to prevent log name collisions.

Error log maximum size

Specifies the maximum size, in megabytes, of the HTTP error log. When the content of the HTTP error log reaches the specified maximum size limit, a [Updated in August 2011] <logname>.<timestamp>.log archive file [Updated in August 2011]

aug2011
is created. The current content of the HTTP error log is then copied to this archive log.

[Updated in August 2011] An example of a file name for this archive log follows::
http_access_11_08_20_16.11.04.log
[Updated in August 2011]
aug2011

The next time the content in the HTTP error log reaches the specified maximum log size, the content of the HTTP error log is again copied to the [Updated in August 2011] <logname>.<timestamp>.log archive file [Updated in August 2011]

aug2011
. The copy process overwrites the current content of the archive file with the most current content of the HTTP error log.

Error log level

Specifies 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, you must specify a large enough log file size in the Error log maximum size field to contain all of the information that is logged.

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.




Related tasks
Configuring Java logging using the administrative console
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=utrb_httperrlogs
File name: utrb_httperrlogs.html