Previous versions of Tomcat (until 5.x) use Apache common logging services for generating logs. A major disadvantage with this logging mechanism is that it can handle only a single JVM configuration and it makes it difficult to configure separate logging for each class loader for independent applications. In order to resolve this issue, Tomcat developers have introduced a separate API for the Tomcat 6 version, that comes with the capability of capturing each class loader activity in the Tomcat logs. It is based on the
By default, Tomcat 7 uses its own Java logging API to implement logging services. This is also called JULI. This API can be found in
TOMCAT_HOME/bin of the Tomcat 7 directory structures (
tomcat-juli.jar). The following screenshot shows the directory structure of the
bin directory where
tomcat-juli.jar is placed. JULI also provides the feature for custom logging for each web application, and it also supports private per-application logging configurations...