You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ravil Zakirov (Jira)" <ji...@apache.org> on 2022/09/12 20:03:00 UTC

[jira] [Commented] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

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

Ravil Zakirov commented on LOG4J2-3035:
---------------------------------------

Is the issue fixed? I still face it in 2.18.0 and 2.17.x.

> Refresh the Stale reference of Log File once the physical file is deleted by external process
> ---------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-3035
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3035
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Plugins
>    Affects Versions: 2.13.3
>            Reporter: Nishit k Ghosh
>            Priority: Major
>             Fix For: 2.16.0
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> Let's assume that an external process deletes the physical log file while a logger is being used by an application.
> In that case the application and the Logger would not know that the physical file doesn't exist. In memory the outputstream reference will remain active and logger will keep on writing into nowhere. Unless the application or container is redeployed / restarted.



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