Log files are rotated by their logger components, either at a scheduled time or when a configured limit on the number of log entries is reached. During rotation, the currently open log file is closed and a new one opened. The logging component fires a JMS message, which is received by a message sink, which adds the closed log file and its type to a queue.

Note: Rotation occurs only if the current log file contains data.

You can schedule file rotation using the schedule property of each logging component (see Search Logging Components and Messages). For example, to rotate the UseSearchEnvironment log hourly, in UseSearchEnvironmentLogger.properties set the following:

schedule=every 1 hour without catch up

For information on how to specify a schedule, see the Scheduler Services section of the Core Dynamo Services chapter in the ATG Platform Programming Guide.

You can also use the dataItemThreshold of each component to trigger log rotation when the specified number of log records is exceeded. If you set both properties, the log will be rotated whenever it exceeds the dataItemThreshold and at the scheduled time, as long as the log file contains at least one log entry.


Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices