private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Table of Contents
This chapter discusses various options for configuring logging.
Jetty provides logging via its own
org.eclipse.jetty.util.log.Logger layer, and does not natively
use any existing Java logging framework. All logging events, produced via
the Jetty logging layer, have a name, a level, and a message. The name is a
FQCN (fully qualified class name) similar to how all existing Java logging
Jetty logging, however, has a slightly different set of levels that it uses internally:
For events serious enough to inform and log, but not fatal.
Debugging events (very noisy).
Exception events that you can safely ignore, but useful for some people. You might see this level as DEBUG under some Java logging framework configurations, where it retains the ignore phrase somewhere in the logging.
Jetty logging produces no FATAL or SEVERE events.
Configure the Jetty logging layer via the
org.eclipse.jetty.util.log.Log class, following these
First from a Classpath Resource called
jetty-logging.properties (if found).
Then from the
Determine the log implementation.
org.eclipse.jetty.util.log.class is defined,
load the class it defines as the logger implementation from the
If the class
org.slf4j.Logger exists in server
classpath, the Jetty implementation becomes
If no logger implementation is specified, default to
By default, the internal Jetty Logging discovery mechanism will load
logging specific properties from a classpath resource called
jetty-logging.properties and then initialize the
Logging from a combination of properties found in that file, along with
any System Properties.
A typical jetty-logging.properties file will include at least the
declaration of which logging implementation you want to use by defining a
value for the
Examples for various logging frameworks can be found later in this documentation.