Re: log4j MDC IRequestLogger

I ended up with a custom RequestCycle @Override public boolean processRequestAndDetach() { boolean result; try { result = processRequest(); } finally { detach(); } popMDC(); return result; } @Override protected void onBeginRequest() { pushMDC(); }

Re: log4j MDC IRequestLogger

Thanks Marios and Martin, François Le 18 févr. 2016 à 08:17, Martin Grigorov a écrit : > Hi Francois, > > You can create a custom RequestLogger that just calls > super.performLogging() and pops the context. > Setup it with

Re: log4j MDC IRequestLogger

Hi Francois, You can create a custom RequestLogger that just calls super.performLogging() and pops the context. Setup it with org.apache.wicket.Application#newRequestLogger() Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Feb 17, 2016 at 2:34 PM, Francois

Re: log4j MDC IRequestLogger

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

log4j MDC IRequestLogger

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