You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/05/12 15:17:00 UTC

[jira] [Commented] (LOG4J2-2840) Log4j2 is not able to detect a deleted log file.

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

Ralph Goers commented on LOG4J2-2840:
-------------------------------------

The bug is that you are trying to delete a file that is being written to. I can think of no logical reason to do that.

> Log4j2 is not able to detect a deleted log file.
> ------------------------------------------------
>
>                 Key: LOG4J2-2840
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2840
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders, Configuration
>    Affects Versions: 2.12.1
>         Environment: Unix server.
>            Reporter: Prateek Sethi
>            Priority: Major
>
> I am using Log4j2 2.12.1.
> And I have configured a rolling file appender to write to a file ( which gets rolled over based on some size limit).
> The issue I am facing is that when active file gets deleted from the backend , log4j2 logger is not able to detect the file deletion and keep on processing the message. I am not able to figure out where the messages are being written. 
> The Status Logger also doesn't show any error events.
> Expected behaviour would have that logger should have created a new file and started writing into it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)