geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <ammul...@alumni.princeton.edu>
Subject Re: Jetty Logging: INFO output
Date Sun, 04 Dec 2005 02:39:32 GMT
On 12/3/05, Jan Bartel <janb@mortbay.com> wrote:
> We will be doing a release anyway for a couple of small things in
> the next day or two. Will let you know when it's done.

Great!

> BTW: what is happening with the JSR77 stuff for the webconsole
> that we were discussing?

I think Joe was looking at that.

Thanks,
    Aaron

> Aaron Mulder wrote:
> > Jan,
> >
> > I don't think DEBUG_VERBOSE made much of a difference, but I had
> > already squashed  most of the Jetty INFO output by setting specific
> > classes to WARN in our log4j.properties, so I'm not sure how obvious
> > it would have been.  It's definitely the case that the messages are
> > going to Log4j, and it seemed to be going through commons logging in
> > the code I was looking at, but I'm not 100% sure.
> >
> > Anyway, we're trying to get the 1.0 release out by ApacheCon, which
> > means around Dec 10-11.  However, given that we'll have to run the TCK
> > again if we upgrade our Jetty version, I think we'll need to stick
> > with whatever we can get by a few days or more in advance of that --
> > which of course is not a lot of time.  I put in a hack for now to
> > squash log output where the logger name starts with "/", so it's not
> > super-critical to get a new Jetty release for G 1.0, but it would be
> > nice to be able to remove that.  :)
> >
> > Thanks,
> >     Aaron
> >
> > On 12/3/05, Jan Bartel <janb-Hmr7moDsS2RBDgjK7y7TUQ@public.gmane.org> wrote:
> >
> >>Aaron,
> >>
> >>I'm a little confused now. When you used -DDEBUG_VERBOSE on the runline
> >>did that change the amount of information that was logged or not?
> >>
> >>If it *did* suppress a lot of INFO messages, then that indicates that
> >>jetty is running with it's own logging mechanism enabled. If it *didn't*,
> >>then that indicates that it is running using commons logging and the usual
> >>commons logging discovery mechanism.
> >>
> >>In any case, the easiest thing to do would be for us to give you
> >>a new Jetty with the JSR154 servlet log message sent to a different
> >>logger (your point #2).
> >>
> >>Also, your suggestion to prefix the ServletContext log messages with
> >>a standard prefix so it can be easily configured in, for eg, log4j is
> >>a good one. We will also implement that. The prefix will most likely
> >>be "org.mortbay.context".
> >>
> >>We'll get the release done ASAP, but it would be helpful to know what
> >>is the timing for a geronimo 1.0 release?
> >>
> >>cheers
> >>Jan
> >>
> >>Aaron Mulder wrote:
> >>
> >>>Further investigation:
> >>>
> >>>org.mortbay.jetty.servlet.JSR154Filter.init:69 is:
> >>> _servletContext.log("JSR154
> >>>unwrappedDispatchSupported="+_unwrappedDispatchSupported);
> >>>
> >>>and the log call there goes to:
> >>>
> >>>org.mortbay.jetty.servlet.ServletHandler$Context.log:1134
> >>>
> >>>and the log variable there turns out to be initialized like this:
> >>>
> >>>_contextLog = LogFactory.getLog(getHttpContext().getHttpContextName());
> >>>
> >>>So it seems like there are two ways to address this:
> >>>
> >>>1) Change ServletHandler.doStart to put a prefix into the context log
> >>>name (like "org.mortbay.jetty.contexts."+getHttpContextName() or
> >>>something)
> >>>
> >>>2) Change JSR154Filter to use a log category of it's own rather than
> >>>the servlet context log call, and set the message to DEBUG instead of
> >>>INFO.
> >>>
> >>>The only options from Geronimo seem a little hacky (suppressing any
> >>>INFO output where the logger name starts with "/", for example).
> >>>
> >>>Thanks,
> >>>    Aaron
> >>>
> >>>On 12/3/05, Aaron Mulder <ammulder-zz2rRYioAk8nkiaMHba4zfZ8FUJU4vz8@public.gmane.org>
wrote:
> >>>
> >>>
> >>>>OK.  I tried:
> >>>>
> >>>>java -DDEBUG_VERBOSE=-1 -jar target/geronimo-1.0-SNAPSHOT/bin/server.jar
-v
> >>>>
> >>>>and I still get:
> >>>>
> >>>>11:59:46,130 INFO  [/] JSR154 unwrappedDispatchSupported=true
> >>>>12:00:03,054 INFO  [/console-standard] JSR154 unwrappedDispatchSupported=true
> >>>>12:00:04,639 INFO  [/console] JSR154 unwrappedDispatchSupported=true
> >>>>
> >>>>Any suggestions?  I'm going to try to track that back to the source.
> >>>>
> >>>>Thanks,
> >>>>   Aaron
> >>>>
> >>>>On 12/3/05, Jan Bartel <janb-Hmr7moDsS2RBDgjK7y7TUQ-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org>
wrote:
> >>>>
> >>>>
> >>>>>Aaron,
> >>>>>
> >>>>>I'm not sure what logging setup you are using with jetty in geronimo.
> >>>>>The normal way to surpress the INFO level messages at jetty startup
is to
> >>>>>set the system property DEBUG_VERBOSE to a negative number on the
runline.
> >>>>>
> >>>>>cheers
> >>>>>Jan
> >>>>>
> >>>>>Aaron Mulder wrote:
> >>>>>
> >>>>>
> >>>>>>I've taken a first stab at reducing our INFO output.  One of
the
> >>>>>>standouts is Jetty, which log various stuff as INFO during startup,
> >>>>>>where the logger name is the web context name (/ or /console
or
> >>>>>>/console-standard, etc.).  Is there any chance of getting a Jetty
> >>>>>>build in the next few days that emits no INFO output during startup?
> >>>>>>
> >>>>>>The problem is, since the log categories are literally only "/"
or
> >>>>>>"/console" or whatever (not AFAICT org.mortbay.jetty./console
or
> >>>>>>something), we can't easily override those categories to log
at only
> >>>>>>WARN or higher.  I mean, we could do it for the console and the
stuff
> >>>>>>we ship, but as soon as the user deployed a new web app, there
would
> >>>>>>be more INFO output again (under their custom context name).
 I'm
> >>>>>>hoping to eliminate INFO output entirely except for stuff like
> >>>>>>"Geronimo server started".  So it would be great to find a way
to
> >>>>>>suppress the "context started" INFO messages from Jetty.
> >>>>>>
> >>>>>>Thanks,
> >>>>>>   Aaron
> >>>>>>
> >>>>>
> >>>>>
> >>
> >
>
>

Mime
View raw message