[
https://issues.apache.org/jira/browse/LOG4J2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333652#comment-15333652
]
Prashant edited comment on LOG4J2-1435 at 6/16/16 12:15 PM:
------------------------------------------------------------
Contents of main log file and rolled log file are different.
We have multiple .ear deployed in Weblogic. Main log file has different A.ear
logs while, rolled.1 has B.ear's logs.
Note: B.ear get calls/messages from A.ear
earlier, when we were on log4j 1.x everything was working just fine..
was (Author: pdshelke):
Contents of main log file and rolled log file are different.
We have multiple .ear deployed in Weblogic. Main log file has different A.ear
logs while, rolled.1 has B.ear's logs.
Note: B.ear get calls/messages from A.ear
> 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: OS : Linux
> Weblogic: 10.3.6.0
> JDK: 1.7.0_55
> 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]
