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 2021/03/02 03:20:00 UTC

[jira] [Closed] (LOG4J2-3032) Memory appender that can be flushed to another appender later

     [ https://issues.apache.org/jira/browse/LOG4J2-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers closed LOG4J2-3032.
-------------------------------
    Resolution: Duplicate

Closing as a duplicate

> Memory appender that can be flushed to another appender later
> -------------------------------------------------------------
>
>                 Key: LOG4J2-3032
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3032
>             Project: Log4j 2
>          Issue Type: New Feature
>            Reporter: Caleb Cushing
>            Priority: Major
>
> Here's [my use case](https://stackoverflow.com/q/66069724/206466 ). Basically, I only want to print test logs if the test fails. I think this could be fixed by having some kind of in-memory appender, just a hashmap would do, and then allow adding a child (or something) appender that could read the entirety of this data and then log it. Maybe just some way to have an appender read a queue of messages and log immediately.



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