[
https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293320#comment-17293320
]
Nishit k Ghosh commented on LOG4J2-3035:
----------------------------------------
The log file is being deleted by a demon process running in the cloud. I think
in my case Question is not why can't we stop the deletion. Question is from
within the code do we have a way to refresh the reference of outputsstream.
> 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.15.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.3.4#803005)
