HTTP error, FRCA, and NCSA access log settings


+

Search Tips   |   Advanced Search

 

To configure the global HTTP error log, and National Center for Supercomputing Applications (NCSA) access log settings for an HTTP inbound channel. If running WAS on z/OS, we can also use this page to configure the global Fast Response Cache Accelerator (FRCA) log settings for an HTTP inbound channel. FRCA logs are a specialized form of NCSA logs and can only be created in a z/OS environment.

To view this admin console page, click...

Servers | Server Types | WebSphere application servers | server_name | HTTP error, NCSA access and FRCA logging

This console page has separate sections for each type of logging. The FRCA logging section only appears if we are running WAS on z/OS.

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.

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 these logs are in NCSA format.

After you configure the HTTP error log, NCSA access logs, and FRCA logs, explicitly enable each type of logging on the settings page for the HTTP channels for which you want a specific types of logging to occur. To view the settings page for an HTTP channel, click...

Servers | Server Types | Application servers | server | Web Container Settings | Web container transport chains | HTTP inbound channel

Avoid trouble: The settings for any of these logs can also be modified on the settings page for a specific HTTP inbound channel. Any changes that you make on the HTTP inbound channel settings page only apply to that specific inbound channel. and override any global settings specified on this page.

Enable logging service at server start-up

Select this option if we want any of the following logging to start when the server starts:

  • NCSA access logging
  • HTTP error logging

Avoid trouble: Even if we select this option, explicitly enable the type of logging to occur on this page and on the settings page for the HTTP transport channel for which you want that type of logging to occur.

Enable NCSA access logging

When selected, a record of inbound client requests that the HTTP transport channel handles is kept in the NCSA access log.

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

NCSA access log maximum size

Maximum size, in megabytes, of the NCSA access log. 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.

Maximum number of historical files

Maximum number of historical versions of the NCSA access log file that are kept for future reference.

NCSA access log format

Specifies which NCSA format is used when logging client access information. If we select Common, the log entries contain the requested resource and a few other pieces of information, but does not contain referral, user agent, and cookie information. If we select Combined, referral, user agent, and 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 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

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.

Maximum number of historical files

Maximum number of historical versions of the Error log file that are kept for future reference.

Error log level

Type of error messages that are included in the HTTP error log. We can select:

Critical

Only critical failures that stop the appserver 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


Set Java logging