[
https://issues.apache.org/jira/browse/LOG4J2-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003276#comment-14003276
]
sivan edited comment on LOG4J2-642 at 5/21/14 9:59 AM:
-------------------------------------------------------
Yes, the list is showing the last modified date and the other files are
waiting for the rollover.
But how the rolled log file on 05/18 contains the entries of 05/19?
Please take a look on the attached image.
05/18 is Sunday and on that day I think there is no log entries and the file
size was 0 bytes. 05/19 is Monday and starts logging in the same file for some
time and rolled over as 'ape1-out-2014-05-18' and creates a new file for 05/19.
This new file contains the entries for only 05/19 and rolled over as
'ape1-out-2014-05-19'.
Also the application has been restarted two times after the patch build has
been deployed. Is anything we need to do for log4j2 in such situations like
calling any clear method or stop method etc..
Can you please go through this scenarios and advise me on this issue?
was (Author: sivan):
Yes, the list is showing the last modified date and the other files are
waiting for the rollover.
But how the rolled log file on 05/18 contains the entries of 05/19?
Please take a look on the attached image.
05/18 is Sunday and on that day I think there is no log entries and the file
size was 0 bytes. 05/19 is Monday and starts logging in the same file for some
time and rolled over as 'ape1-out-2014-05-18' and creates a new file for 05/19.
This new file contains the entries for only 05/19 and rolled over as
'ape1-out-2014-05-19'.
Can you please go through this scenario?
> Mismatch in Rollover date and log entry date in the log file
> ------------------------------------------------------------
>
> Key: LOG4J2-642
> URL: https://issues.apache.org/jira/browse/LOG4J2-642
> Project: Log4j 2
> Issue Type: Bug
> Environment: Java 7
> Reporter: sivan
> Attachments: logFolder.png, rolledLogFile.png
>
>
> This is an issue with the rollbacking of the log file. The file is rollbacked
> as inst4-out-2014-05-16.log. But the log entry is created on 2014-05-19. So
> many log files are rollbacked like this. The configuration is as follows. Can
> you please advise why this is happening?
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration>
> <properties>
> <property
> name="logPattern">log_type_%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 />
> <SizeBasedTriggeringPolicy />
> </Policies>
> <DefaultRolloverStrategy compressionLevel="0" max="3"/>
> </RollingFile>
> </appenders>
> <loggers>
> <AsyncLogger name="sso" level="info" includeLocation="true"
> additivity="false">
> <AppenderRef ref="RollingFile"/>
> </AsyncLogger>
> <AsyncLogger name="webservice" level="info"
> includeLocation="true" additivity="false">
> <AppenderRef ref="RollingFile"/>
> </AsyncLogger>
> <root level="info">
> <AppenderRef ref="Console"/>
> </root>
> </loggers>
> </configuration>
> {code}
> Below is the Log Entry from log file.
> {code}
> log_type_webservice|job-945|ump-standard-jobType-203-sessKey-job-945|05/19/2014
>
> 15:29:29.374|INFO|com.mmp.webservice.wsFactory|factory|109|Service#FirmSTP#$$#Starts
> creating the ws client: FirmSTP
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
