You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2021/04/07 04:22:00 UTC

[jira] [Commented] (LOG4J2-3066) Improve Socket Appender error handling

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

Gary D. Gregory commented on LOG4J2-3066:
-----------------------------------------

Should this be made to work in cunjunction with the failover appender? I can see this being handy with the database appenders.

At work we've done this kind of stuff with a JMS appender and an ETL process that reads from the queue and writes to the database.

> Improve Socket Appender error handling
> --------------------------------------
>
>                 Key: LOG4J2-3066
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3066
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 2.14.1
>            Reporter: Ralph Goers
>            Priority: Major
>
> When the SocketAppender is unable to connect to any hosts it should start logging to a file on disk similar to the way the FlumeAppender works. Once the connection is re-established all queued events should be removed from the file and sent.



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