Log4j2 daily log files

Question

I want my log files created by log4j2 to have the date pattern in their file name, including the current active file. That is, if todays date is 2016-12-15, I want the current log-file to be lager-2016-12-15.log. When the date changes, I want a new file to be created named lager-2016-12-16.log.

With RollingFileAppender I am not able to get the current active log file to have date pattern in the filename. My Log4j2.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration>
    <Properties>
        <Property name="layoutPattern">%d{ISO8601} [%t] %-5p [%X{REQUEST_ID}] [%X{CLIENT_ID}] [%X{USER_ID}] %c- %m%n</Property>
        <Property name="logDir">${sys:catalina.home}/logs/</Property>
        <Property name="fileName">${logDir}lager-${date:yyyy-MM-dd-HHmm}.log</Property>
        <Property name="filePattern">${logDir}lager-%d{yyyy-MM-dd-HHmm}.log</Property>
    </Properties>
    <Appenders>
        <RollingFile name="LAGER" append="true"
                 fileName="${fileName}"
                 filePattern="${filePattern}">
            <PatternLayout pattern="${layoutPattern}" charset="UTF-8"/>
            <Policies>
                <TimeBasedTriggeringPolicy interval="1" modulate="true"/>
            </Policies>
        </RollingFile>
    </Appenders>
    <loggers>
        <Logger name="org.apache.catalina.core.ContainerBase.[Catalina].[localhost]" level="WARN" additivity="false">
            <AppenderRef ref="LAGER" />
            <AppenderRef ref="CONSOLE"/>
        </Logger>
        <Root level="INFO">
            <AppenderRef ref="LAGER"/>
            <AppenderRef ref="CONSOLE"/>
        </Root>
    </loggers>
</Configuration>

With this config the copying when it rolls over is messed up. Removing the date pattern from the fileName property fixes this, but the the current file does not have the date in its name.

I am running this on a tomee 7.0.1.

Answer 1

There may already be an outstanding feature request for this. Would this match your requirements? https://issues.apache.org/jira/browse/LOG4J2-1101

If so, please comment on that JIRA ticket. If you're able to contribute a patch (ideally with unit test) it is likely to get resolved quickly.