Thanks for getting back so quick. I wasn’t sure as for embedded it wasn’t clear About logging configuration and since before we just used system properties After that didn’t work we just were trying various things.
I made sure both the jar and properties file was in the classapath And our properties file is the basic one from doc # Do not condense logger names. org.eclipse.jetty.logging.appender.NAME_CONDENSE=false # By default, log at INFO level all Jetty loggers. org.eclipse.jetty.LEVEL=DEBUG # However, the Jetty client loggers log at DEBUG level. org.eclipse.jetty.client.LEVEL=DEBUG restarted things and no logging. You mentioned transitive dependencies which currently we are not loading anything and the documentation for logging doesn’t mention anything. Shouldn’t I be able to just set these two system properties and include the jar file In the classpath to turn on logging? And for that matter just the first one right? -Dorg.eclipse.jetty.LEVEL=DEBUG -Dorg.eclipse.jetty.client.LEVEL=DEBUG I'm pretty sure were missing something fundamentally but not sure what. Again thanks for getting back to me Dan -----Original Message----- From: jetty-users <[email protected]> On Behalf Of Simone Bordet Sent: Friday, May 21, 2021 1:02 PM To: JETTY user mailing list <[email protected]> Subject: EXT: Re: [jetty-users] jetty 11 logging Hi, On Fri, May 21, 2021 at 6:00 PM Nault, Danny (GE Digital) <[email protected]> wrote: > > We just switched to Jetty 11.0.2 and are running embedded. > > I know there were changes to logging but after reading the doc > > And trying a number of different things I still cannot get > > Any logging to output. > > > > I’m more interested in being able to get the same logging as 9.4.40 > using > > -Dorg.eclipse.jetty.LEVEL=DEBUG \ > > -Dorg.eclipse.jetty.io.ssl.LEVEL=DEBUG \ > > -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLo > g \ > > > > I know by the docs that the last property appears to no longer exist > and it defaults To Slf4j. That is correct, the last property is ignored. > I tried > > Putting jetty-logging-properties in the class path Under $JETTY_HOME, > I have a resources directory with the same jetty-logging properties > Using the first 2 -D options above. You said you are running embedded, so $JETTY_HOME and resources/ directory are irrelevant, no? Make sure you have jetty-logging.properties in the classpath, and make sure you have jetty-slf4j-impl-<jetty-version>.jar in the classpath too (along with the transitive dependencies you need). -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ jetty-users mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users _______________________________________________ jetty-users mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
