[
https://issues.apache.org/jira/browse/LOG4J2-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017448#comment-14017448
]
sivan commented on LOG4J2-659:
------------------------------
Thanks for your response.
I tried with $$$date and $$date and size based triggering policy in my
development machine. Both resolved the path successfully.
Please find the attached debug trace on application start up
Below is the bebug trace on log file rollover. ".\" is the application path in
my dev machine.
2014-06-04 12:11:41,908 DEBUG RollingFileManager executing synchronous
FileRenameAction[.\PS0565-out.log to .\2014-06\PS0565-out-2014-06-04.log,
renameEmptyFiles=false]
Today I analyzed the log4j folder in our production environment and the common
behaviours found are as below.
1. 06/03 files are properly rolled over to the 2014-06 folder.
2. Some 05/30 and 05/31 files are also rolled over to the 2014-06 folder.
3. 06/02 and 06/01 files are rolled over to the 2014-05 folder.
Can you please advise what else I need to do to resolve this issue?
> Log files not properly rolled over to the folder.
> -------------------------------------------------
>
> Key: LOG4J2-659
> URL: https://issues.apache.org/jira/browse/LOG4J2-659
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0-rc1
> Environment: Java 7
> Reporter: sivan
> Priority: Critical
> Attachments: $$$date_debug _trace.txt, $$date_debug _trace.txt,
> 2014-05.png, 2014-06.png, log4j.png
>
>
> This is happening in our production environment. My application is using
> rolling file appender. In the beginning of this month the files are not
> rolled over to the folders as expected.
> 2014-05 folder contains 06/01 and 06/02 rolled over files and 2014-06 folder
> contains 05/30 file
> In another server 2014-06 folder is not yet created still now and the log
> files on 06/01 and 06/02 are rolled over to the 2014-05 folder.
> Screen shots have been attached. In the screen shots file names are masked
> due to the compliance rules.
> Can you please advise what I need to do for resolving this issue?
> The configuration is as below.
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration>
> <properties>
> <property name="logPattern">%c|%K{sessionId}|%t|%d{MM/dd/yyyy
> HH:mm:ss.SSS}|%p|%C|%M|%L|%K{msg}%n</property>
> <property
> name="filePattern">${sys:logfilepath}//$${date:yyyy-MM}//${sys:oft.appserver}-out-%d{yyyy-MM-dd}.log</property>
> <property
> name="fileName">${sys:logfilepath}//${sys:oft.appserver}-out.log</property>
> </properties>
> <appenders>
> <Console name="Console" target="SYSTEM_OUT">
> <PatternLayout pattern="logPattern"/>
> </Console>
> <RollingFile name="RollingFile" fileName="${fileName}"
> filePattern="${filePattern}">
> <PatternLayout>
> <pattern>${logPattern}</pattern>
> </PatternLayout>
> <Policies>
> <TimeBasedTriggeringPolicy />
> </Policies>
> </RollingFile>
> </appenders>
> <loggers>
> <AsyncLogger name="logtype" level="info" includeLocation="true"
> additivity="false">
> <AppenderRef ref="RollingFile"/>
> </AsyncLogger>
> <root level="info">
> <AppenderRef ref="Console"/>
> </root>
> </loggers>
> </configuration>
--
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
