[
https://issues.apache.org/jira/browse/LOG4J2-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-612:
-------------------------------
Labels: Rollover (was: )
> RollingFileAppender does not reuse PatternParser
> ------------------------------------------------
>
> Key: LOG4J2-612
> URL: https://issues.apache.org/jira/browse/LOG4J2-612
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0-rc1
> Reporter: Jan Stolze
> Labels: Rollover
>
> Creating a RollingFileAppender leads to creation of a RollingFileManager
> which creates a PatternProcessor, which creates a PatternParser.
> The PatternParser will start out a plugin find expedition on the classpath
> which takes some time.
> This is done for every RollingFileAppender you create. In my case the log
> file naming pattern is always the same for all log files, so I do not see the
> necessity for this plugin finding expedition. For instance PatternLayout does
> not do this as long as you supply a Configuration object which reuses the
> PatternParser for this Configuration object.
> Can RollingFileManager follow the same pattern as PatternLayout does?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
