From: rjung Date: Sun, 15 Jul 2007 17:03:25 +0000 (+0000) Subject: Correct j.u.l log levels in JULI docs. X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=bf6263d9b9fd9377c8aac1fe17a9a25f033dfd95;p=tomcat7.0 Correct j.u.l log levels in JULI docs. git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@556431 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index eb5e5d003..298df62ce 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -15,6 +15,13 @@
+ + + + Correct j.u.l log levels in JULI docs. (rjung) + + + diff --git a/webapps/docs/logging.xml b/webapps/docs/logging.xml index 948bf7f58..e13cb8e75 100644 --- a/webapps/docs/logging.xml +++ b/webapps/docs/logging.xml @@ -171,8 +171,8 @@

The default logging.properties specifies a ConsoleHandler for routing logging to stdout and - also a FileHandler. A handler's log level threshold can be set using SEVERE, CONFIG, INFO, - WARN, FINE, FINEST or ALL. The logging.properties shipped with JDK is set to INFO. You + also a FileHandler. A handler's log level threshold can be set using SEVERE, WARNING, INFO, + CONFIG, FINE, FINER, FINEST or ALL. The logging.properties shipped with JDK is set to INFO. You can also target specific packages to collect logging from and specify a level. Here is how you would set debugging from Tomcat. You would need to ensure the ConsoleHandler's level is also set to collect this threshold, so FINEST or ALL should be set. Please refer to Sun's java.util.logging