[
https://issues.apache.org/jira/browse/LOG4J2-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727857#comment-15727857
]
Ralph Goers commented on LOG4J2-1725:
-------------------------------------
This happens because the pattern is managed by the RollingFileManager, not the
appender. When a reconfiguration occurs new Appenders are created but if a
Manager already exists for the target file then it is reused to prevent any
data loss or corruption by closing the outputstream and creating a new one. The
RollingFileManager was recently updated to allow the triggering policy and
rollover strategy to be updated. A similar approach could be taken for the
pattern.
> RollingFileAppender's filePattern not reloaded when using monitorInterval
> -------------------------------------------------------------------------
>
> Key: LOG4J2-1725
> URL: https://issues.apache.org/jira/browse/LOG4J2-1725
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Benjamin Jaton
>
> Using the configuration below:
> {code}<?xml version="1.0" encoding="UTF-8"?>
> <Configuration status="info" monitorInterval="2">
> <Appenders>
> <RollingFile name="MyRollingFile"
> fileName="/usr/local/apps/testlogging/logs/app.log"
> filePattern="/usr/local/apps/testlogging/logs/app.log.%i">
> <PatternLayout>
> <Pattern>%d %p %c{1.} [%t] %m%n</Pattern>
> </PatternLayout>
> <Policies>
> <SizeBasedTriggeringPolicy size="100MB"/>
> </Policies>
> <DefaultRolloverStrategy max="10"/>
> </RollingFile>
> </Appenders>
> <Loggers>
> <Root level="info" includeLocation="false">
> <AppenderRef ref="MyRollingFile"/>
> </Root>
> </Loggers>
> </Configuration>{code}
> Updating the filePattern to app.log.%i.zip won't be taken into account
> dynamically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
