It is possible that an appender might call some other component that does its
own logging. The problem is that it is too easy (or difficult to prevent) to
have the configuration set up so that the logs from that component end up going
back through the same appender. For example, if you are usi
It's generally recommended to use the StatusLogger implementation of Logger
when logging inside log4j extensions like that. All log4j core components
follow this idea.
On 7 April 2016 at 01:13, Maple Wang wrote:
> Hi,
>
>
>
> We are implementing a function with self-defined appender in log4j2.x,
