![]() |
![]() |
||
![]() ![]() |
Logging Fast Response Cache Accelerator requests |
||
This section provides information on logging FRCA requests. A general overview discusses the Cache Accelerator access log path and name. Links to related topics appear at the end of this section.
Understanding the Cache Accelerator access logThe IBM HTTP Server can optionally create a log file that records requests served by the Cache Accelerator. Enable the Cache Accelerator access log if you want to maintain a record of requests served by the Cache Accelerator. You can log requests that the Cache Accelerator does not log, using the normal Apache logging directives in separate log files. Use this log if you have enabled the Cache Accelerator for improved performance, and want to record information about requests served from the Cache Accelerator. This log provides a useful way to verify enabled caching and cached files. Even though a file caches, the sequence of events on a given connection determines whether or not the file serves from the cache. The log file has a date stamp automatically appended to its name. Every day at midnight the server closes the current access log and creates a new one. This action enables the log file to process without having to stop and restart the server. Under heavy load conditions the log file can grow rapidly. Provide sufficient space on the hard drive for storage. For each request served out of the Cache Accelerator, a new entry in the access log shows the:
A new entry can also optionally show the:
Specifying the path and file name for the Cache Accelerator access logYou can specify the path and file name of the Cache Accelerator access log file from the Administration Server.
(Back to the top) |