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 <[email protected]> wrote: > Hi, > > > > We are implementing a function with self-defined appender in log4j2.x, in > this appender, we forward LogEvent to other function modules, and in those > function modules we also log some messages to this appender , so you must > understand that recursive call will happen sometimes. For current > implementation of log4j2.5, this kind of recursive call will be totally > blocked from appender, but this is not what we expect. Actually, we are > aware of this recursive call situation and we will handle it in appender by > ourselves to meet function requirement, it worked in log4j1.x, but it's not > working in log4j2.x because of recursive call check for appender, is it > possible to disable it? Or at least to disable recursive call check for > specific appender. > > > > Best regards. > > -- Matt Sicker <[email protected]>
