[
https://issues.apache.org/jira/browse/LOG4J2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333638#comment-15333638
]
Prashant edited comment on LOG4J2-1435 at 6/16/16 11:59 AM:
------------------------------------------------------------
For first 3 rolls everything works fines, but as load increases(for first 300K
records I havent seen this issue!) this issue comes.
PFA Capture2.PNG and you will see weird behavior.
Also maximum roll should have oldest timestamp, but for roll 4 you can see its
having latest timestamp which is also look like an issue.
was (Author: pdshelke):
For first 3 rolls everything works fines, but as load increases(for first 300K
records I havent seen this issue!) this issue comes.
PFA Capture2.PNG and you will see weird behavior.
> 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
> Environment: _Can you add some detail here? What is your operating
> system, Java version, WebLogic version?_
> Reporter: Prashant
> Priority: Critical
> Attachments: Capture.PNG, Capture2.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: [email protected]
For additional commands, e-mail: [email protected]
