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 <[EMAIL PROTECTED]> 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
> >
>
>
