logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: Log4j 2.x Web app initialization logging
Date Thu, 04 Sep 2014 16:14:03 GMT
Perhaps we should log to StatusLogger rather than to ServletContext.log()?
I mean, we even have an appender that goes to the ServletContext log, so it
might be a better idea to just use the StatusLogger as usual (unless an
error occurs?).


On 4 September 2014 11:07, Gary Gregory <garydgregory@gmail.com> wrote:

> Should be log only if some condition is met? Like the status logger level
> set to DEBUG?
>
> Gary
>
>
> On Thu, Sep 4, 2014 at 12:03 PM, Mikael Ståldal <
> mikael.staldal@appearnetworks.com> wrote:
>
> > Log4jServletContainerInitializer, Log4jServletContextListener,
> > Log4jServletFilter and Log4jWebInitializerImpl log some stuff using
> > ServletContext.log() at startup and shutdown.
> >
> > Why? I find this logging noisy when done when everything works fine.
> >
> > --
> > Mikael Ståldal
> > Chief Software Architect
> > *Appear*
> > Phone: +46 8 545 91 572
> > Email: mikael.staldal@appearnetworks.com
> >
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker <boards@gmail.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message