You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/04/12 15:58:25 UTC

[jira] [Commented] (LOG4J2-1266) at midnight Log4j2 continue loging the the rolled file and overwrite yesterday logs

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

Remko Popma commented on LOG4J2-1266:
-------------------------------------

Perhaps we need to put a CountDownLatch in the async rollover action to ensure that the synchronous (rename) task is complete before we start the async (compress) task. 

> at midnight Log4j2 continue loging the the rolled file and overwrite yesterday logs
> -----------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1266
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1266
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.4
>         Environment: Jboss, Java 1.7
>            Reporter: Hassan morsy
>
> the problem is the log at midnight renamed with the date and the index. just before the file got compre ssed it got overwritten. with the new days logs for few seconds. I endup by very short compress file and lose the yesterday logs.
> when I start gz the file it stoped writing to the file.
> when I used %1 it did create create two files app-date-2-.log.gz the worthe few seconds of log after 12:00 and app-date-1.log.gz yesterday logs
> if I don't gz the file it continue writing to both file app.log and app-date.log



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org