[
https://issues.apache.org/jira/browse/LOG4J2-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764685#comment-13764685
]
Jesse Docken commented on LOG4J2-398:
-------------------------------------
I'm still observing the same behavior, although now it generates an error if
the fileName attribute is omitted (which is most likely the correct behavior).
Am I simply configuring it improperly? What would be the correct way to
configure an appender such that the filename always contains the date and time
of when the file was initially generated (i.e., when the program began to run)?
We don't want the filename to be lacking this timestamp at any point in time.
> DateLookup not parsed for FastRollingFile appender
> --------------------------------------------------
>
> Key: LOG4J2-398
> URL: https://issues.apache.org/jira/browse/LOG4J2-398
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0-beta8
> Environment: Operating System: Windows Server 2008 R2 SP1
> Java Runtime: 1.7.0_03-x64
> Reporter: Jesse Docken
>
> I'm trying to create a Log4j2 configuration file that will create a log file
> using DateLookup so that the current date and time are in the filename (so it
> matches the logging used in our other products). This is what the appender
> configuration looks like:
> {code:borderStyle=solid|language=XML}
> <FastRollingFile name="Rolling" fileName="log/$${date:yyyyMMdd-HHmmss} -
> myApp.log" filePattern="log/$${date:yyyyMMdd-HHmmss} - myApp-%i.log">
> <immediateFlush>true</immediateFlush>
> <suppressExceptions>false</suppressExceptions>
> <PatternLayout>
> <pattern>%d %p %c{1.} [%t] $${env:USER} %m%n</pattern>
> </PatternLayout>
> <Policies>
> <OnStartupTriggeringPolicy />
> <SizeBasedTriggeringPolicy size="100 MB"/>
> </Policies>
> </FastRollingFile>
> {code}
> However when the log file is generated the filename is "${date". I've tried
> different variations and haven't been able to get this lookup to work at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
