[
https://issues.apache.org/jira/browse/LOG4J2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333626#comment-15333626
]
Remko Popma commented on LOG4J2-1435:
-------------------------------------
Hmm, looking at that screenshot, it looks as if the problem is the opposite:
the main log file is twice as big as the rolled file.
Based on the file size, it looks like the main log file, instead of starting
from scratch, takes a copy of the rolled file and appends to it.
Can you confirm from the log contents that this is what is happening? Do the
contents of the files look something like this?
||main log file||rolled log file||
|9:00 A|9:00 A|
|9:01 B|9:01 B|
|9:02 C|9:02 C|
|9:03 D| |
|9:04 E| |
|9:05 F| |
> Log4j2 writing logs to already rolled file
> ------------------------------------------
>
> Key: LOG4J2-1435
> URL: https://issues.apache.org/jira/browse/LOG4J2-1435
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators, Performance Benchmarks
> Affects Versions: 2.6.1
> Reporter: Prashant
> Priority: Critical
> Attachments: Capture.PNG, log4j.xml
>
>
> Recently we have migrated from log4j 1.x to 2.6.1
> I am seeing loggers are being written to rolled file along with main log file.
> This is observed mainly if I am pushing load of 400k records.
> PFA log4j xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
