[
https://issues.apache.org/jira/browse/LOG4J2-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237861#comment-15237861
]
Ralph Goers commented on LOG4J2-1266:
-------------------------------------
Web applications and EJBs run as separate "applications" with their own
ClassLoaders, so the only way you could solve this would be to put the log4j
classes at the container level. How you would do that depends on what J2EE
container you are using. If you do that then the configuration and Managers
should be shared across all the applications running the int container.
> 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: [email protected]
For additional commands, e-mail: [email protected]