Re: log4j MDC IRequestLogger

[mscoon <ms...@gmail.com>]

Hi,

In a similar situation we have sub-classed RequestLogger and we are
clearing the thread context in the end of MyRequestLogger.log(), so that
the thread context is available when super.log() is called. It is not as
clean as using AbstractRequestCycleListener.onDetach, but it works.

Marios

On Wed, Feb 17, 2016 at 3:34 PM, Francois Meillet <
francois.meillet@gmail.com> wrote:

> Dear All,
>
> I use the Mapped Diagnostic Context concept
> https://logging.apache.org/log4j/2.x/manual/thread-context.html).
>
> Using log4j 2.x and a specific AbstractRequestCycleListener,
> I overrided onBeginRequest() to perform a ThreadContext.push(id)
> and onDetach(RequestCycle cycle) to perform a ThreadContext.pop();.
>
> So far so good for all the logs but the IRequestLogger's logs.
>
> I notice that the IRequestLogger # performLogging() is called after the
> RequestCycle # onDetach() has been called.
>
> I would like it to happen before !
> Is that possible ?
>
>
> François
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>