[
https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293343#comment-17293343
]
Ralph Goers commented on LOG4J2-3035:
-------------------------------------
If you are interested in contributing a few patches you may want to sign an
submit an [ICLA|https://www.apache.org/licenses/contributor-agreements.html].
It you want to become a committer I would suggest you read through the [Log4j2
Guidelines|http://logging.apache.org/log4j/2.x/guidelines.html] and the ASF
"[How it works|https://www.apache.org/foundation/how-it-works.html]"; pages.
We always welcome patches and hope people will be interested enough to become
committers.
As Carter mentioned, for now just fork
[https://github.com/apache/logging-log4j2,|https://github.com/apache/logging-log4j2]
make your modifications, and then create a pull request for us to review.
Discussions of ideas can happen in specific Jira issues but usually it is
easier to discuss things on the [dev mailing
list|http://logging.apache.org/log4j/2.x/mail-lists.html].
> 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)
