geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <>
Subject Re: [jira] Created: (GERONIMO-806) Reduce log output
Date Mon, 25 Jul 2005 03:47:01 GMT
On Sun, 24 Jul 2005, Jeff Genender wrote:
> Is this a bug or a log4j filter setting?

	True, it is a Log4j setting; the "bug" is to ensure that we think
about it and someone acts on it.  :)  I mean, I think it's a "problem"
that we generate too much log data for irrelevant stuff, but not a bug in
the code per se.

	I would lean toward setting the log level to WARN for every 
third-party package we ship, except maybe OpenEJB and TranQL.  I could 
maybe be talked into INFO for some, but there would have to be something 
definite we want to be abel to see in there.

	We may also consider using a different log4j file for our release
builds, so Geronimo developers can see more server internals during server
development.  But my experience as an application developer is that I'm
not real keen on seeing server log output; I only want to see problems
from the server, with the more verbose logging reserved for my


P.S. Sorry Alan

> Aaron Mulder (JIRA) wrote:
> > Reduce log output
> > -----------------
> > 
> >          Key: GERONIMO-806
> >          URL:
> >      Project: Geronimo
> >         Type: Bug
> >   Components: general, usability  
> >     Versions: 1.0-M3    
> >     Reporter: Aaron Mulder
> >      Fix For: 1.0-M5
> > 
> > 
> > Cut down on the default log output from third-party libs.  In particular, org.apache.jasper.compiler.SmapUtil
and Jetty (based on my own logs), though I've also seen Digester go crazy before.
> > 

View raw message