[ 
https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964851#comment-15964851
 ] 

Ralph Goers commented on LOG4J2-1185:
-------------------------------------

You have to omit the fileName attribute entirely. The rolling file appender 
will write directly to the target file using its pattern.

> Ability to change the fileName dynamically in RollingFileAppender
> -----------------------------------------------------------------
>
>                 Key: LOG4J2-1185
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1185
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 2.1
>            Reporter: Dhwaneet Bhatt
>            Assignee: Ralph Goers
>             Fix For: 2.8
>
>
> Right now RollingFileAppender rolls over the current file with fileName to 
> the one generated by FilePattern. However, logging always continues in the 
> same fileName i.e. fileName once created cannot be changed.
> Property Substitution is only once during initialization, fileName is never 
> changed after RollingFileManager is initialized. The RollingFileManager is 
> very tightly tied up to the fileName attribute.
> Consider that I want to name my log files like this using RollingFileAppender:
> mylog-2015-10-30.log
> mylog-2015-10-29.log
> mylog-2015-10-28.log
> There is no good way to achieve this, because even after rolling over the 
> file, the fileName would still remain the same. If I initialized my fileName 
> using $\{date:yyyy-MM-dd\}, date would be substituted only once during 
> initialization and it would never change, always continue to log in the same 
> log file (until I restart my application).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to