[jira] [Commented] (LOG4J2-1435) Log4j2 writing logs to already rolled file

["Ralph Goers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758912#comment-16758912 ] 

Ralph Goers commented on LOG4J2-1435:
-------------------------------------

Is this still an issue? In looking at the configuration this can't possibly work if there are multiple log4j instances in the same VM. The file size is obtained from the file when it is first opened and cached and then that value is incremented by the size of each log event as each is written. If multiple Log4j instances are logging to the same file then the size calculations will be very incorrect. If the Log4j jars are in the container's classLoader then it should work fine.

> 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
> Log4j version tested: 2.3 and 2.6.1
>            Reporter: Prashant
>            Priority: Critical
>         Attachments: 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
(v7.6.3#76005)