[
https://issues.apache.org/jira/browse/LOG4J2-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Asbach updated LOG4J2-2832:
------------------------------------
Description:
If you configure a `RollingFileAppender` with no `fileName` configured the
mesagge refrences a non existing `Strategy`:
{code:java}
LOGGER.error("RollingFileAppender '{}': When no file name is provided a
DirectFilenameRolloverStrategy must be configured", getName());
{code}
https://github.com/apache/logging-log4j2/blob/log4j-2.13.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/RollingFileAppender.java#L141
A similar problem was already reported and fixed in:
https://issues.apache.org/jira/browse/LOG4J2-2547
was:
If you configure a `RollingFileAppender` with no `fileName` configured the
mesagge refrences a non existing `Strategy`:
{code:java}
LOGGER.error("RollingFileAppender '{}': When no file name is provided a
DirectFilenameRolloverStrategy must be configured", getName());
{code}
A similar problem was already reported and fixed in:
https://issues.apache.org/jira/browse/LOG4J2-2547
> Error message contains reference to non-existent
> DirectFilenameRolloverStrategy
> -------------------------------------------------------------------------------
>
> Key: LOG4J2-2832
> URL: https://issues.apache.org/jira/browse/LOG4J2-2832
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.13.2
> Reporter: Benjamin Asbach
> Priority: Minor
>
> If you configure a `RollingFileAppender` with no `fileName` configured the
> mesagge refrences a non existing `Strategy`:
> {code:java}
> LOGGER.error("RollingFileAppender '{}': When no file name is provided a
> DirectFilenameRolloverStrategy must be configured", getName());
> {code}
> https://github.com/apache/logging-log4j2/blob/log4j-2.13.2/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/RollingFileAppender.java#L141
> A similar problem was already reported and fixed in:
> https://issues.apache.org/jira/browse/LOG4J2-2547
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
