RollingFileAppender
extends {@link FileAppender} to backup the log filesdepending on {@link RollingPolicy} and {@link TriggeringPolicy}. To be of any use, a RollingFileAppender
instance must have both a RollingPolicy
and a TriggeringPolicy
set up. However, if its RollingPolicy
also implements the TriggeringPolicy
interface, then only the former needs to be set up. For example, {@link TimeBasedRollingPolicy} acts both as aRollingPolicy
and a TriggeringPolicy
.
RollingFileAppender
can be configured programattically or using {@link org.apache.log4j.joran.JoranConfigurator}. Here is a sample configration file:
<?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE log4j:configuration> <log4j:configuration debug="true"> <appender name="ROLL" class="org.apache.log4j.rolling.RollingFileAppender"> <rollingPolicy class="org.apache.log4j.rolling.TimeBasedRollingPolicy"> <param name="FileNamePattern" value="/wombat/foo.%d{yyyy-MM}.gz"/> </rollingPolicy> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%c{1} - %m%n"/> </layout> </appender> <root"> <appender-ref ref="ROLL"/> </root> </log4j:configuration>
This configuration file specifies a monthly rollover schedule including automatic compression of the archived files. See {@link TimeBasedRollingPolicy} for more details. @author Heinz Richter @author Ceki Gülcü @since 1.3
|
|