Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 50579 invoked by uid 500); 10 Apr 2002 07:54:01 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 50568 invoked from network); 10 Apr 2002 07:54:01 -0000 Date: 10 Apr 2002 07:54:14 -0000 Message-ID: <20020410075414.4020.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: cocoon-dev@xml.apache.org Cc: Subject: DO NOT REPLY [Bug 7909] New: - Setting Log-Level to FATAL-ERROR is not possible X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7909 Setting Log-Level to FATAL-ERROR is not possible Summary: Setting Log-Level to FATAL-ERROR is not possible Product: Cocoon 2 Version: 2.0.2 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: core AssignedTo: cocoon-dev@xml.apache.org ReportedBy: heid@fh-heilbronn.de [Using Cocoon 2.0.2 in Jetty 4.0.0 on Win 2000 with JDK 1.4] I have changed all log-level attributes in logkit.xconf and web.xml to FATAL-ERROR but every debug message is printed out into the four log files and(!) on stdout. It seems to work for 2.0.1 not for 2.0.2 --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org