You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/15 02:05:00 UTC
[jira] [Work logged] (LOG4J2-2680) Not compressing after rolling a
file using copy and truncation method
[ https://issues.apache.org/jira/browse/LOG4J2-2680?focusedWorklogId=312626&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-312626 ]
ASF GitHub Bot logged work on LOG4J2-2680:
------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Sep/19 02:04
Start Date: 15/Sep/19 02:04
Worklog Time Spent: 10m
Work Description: rgoers commented on pull request #304: Fix LOG4J2-2680: Not compressing after rolling a file using copy and …
URL: https://github.com/apache/logging-log4j2/pull/304
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 312626)
Remaining Estimate: 40m (was: 50m)
Time Spent: 20m (was: 10m)
> Not compressing after rolling a file using copy and truncation method
> ---------------------------------------------------------------------
>
> Key: LOG4J2-2680
> URL: https://issues.apache.org/jira/browse/LOG4J2-2680
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2, 2.7, 2.8, 2.8.1, 2.8.2, 2.9.0, 2.9.1, 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1
> Environment: Windows 2016 Server
> Reporter: Guillermo Xavier Hurtado Garcia
> Priority: Critical
> Fix For: 2.12.1
>
> Attachments: fix.png
>
> Original Estimate: 1h
> Time Spent: 20m
> Remaining Estimate: 40m
>
> When log file has reached rolling size, method "execute" on "org.apache.logging.log4j.core.appender.rolling.action.FileRenameAction" class run as follows:
> 1. Move the log file to a new one using a new name;
> 2. If move fails, then it renames the log file;
> 3. If rename fails, then it copies the original file and then:
> 3.1 Deletes original file;
> 3.2 if delete fails, then it truncates the original file contents.
> Steps 2 and 3 are executed usually when original file is locked; after any successful step, the returning value should be "true", however after successfully executing step 3.2 it remains "false", avoiding the compression algorithm to be executed.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)