You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2022/09/08 05:43:00 UTC

[jira] [Commented] (LOG4J2-3525) Log altered after rolling

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

Ralph Goers commented on LOG4J2-3525:
-------------------------------------

I am fairly certain we have unit tests for this scenario. You have status="trace" set in the configuration. Can you please provide the status logs from the time of rollover?

> Log altered after rolling
> -------------------------
>
>                 Key: LOG4J2-3525
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3525
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.17.1
>            Reporter: Anton Sutopo
>            Priority: Critical
>         Attachments: 2K7BUsOOYB.png, log4j2.xml
>
>
> Hi all, 
> I found log altered after daily rolling happen and this is only happen on  certain log. In my case is on stdout.log. for example is the log suppose only contain for date 2022-05-28 but the content is altered by log from date 2022-05-29. Here is the configuration i used this is for java web application  [^log4j2.xml]
> !2K7BUsOOYB.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)