Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 15526 invoked from network); 22 Jan 2006 08:25:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jan 2006 08:25:32 -0000 Received: (qmail 61449 invoked by uid 500); 22 Jan 2006 08:25:31 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 60908 invoked by uid 500); 22 Jan 2006 08:25:29 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 60897 invoked by uid 99); 22 Jan 2006 08:25:29 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2006 00:25:28 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 88D31CB for ; Sun, 22 Jan 2006 09:25:07 +0100 (CET) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: commons-dev@jakarta.apache.org Date: Sun, 22 Jan 2006 08:25:07 -0000 Message-ID: <20060122082507.11496.36525@ajax.apache.org> Subject: [Jakarta-commons Wiki] Update of "Logging/FrequentlyAskedQuestions" by SimonKitching X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification. The following page has been changed by SimonKitching: http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions The comment on the change is: Moved FAQ info in static webpages to wiki ------------------------------------------------------------------------------ The JULI module in Apache Tomcat provides adapters from the java.util.logging API log4j. This is of course not an option for code that may be run in JVMs prior to 1.4. The java.util.logging system can also be awkward to set up. + + + == Is JCL Thread Safe? == + + JCL doesn't (and cannot) impose any requirement on thread safety on the underlying implementation and thus its SPI contract doesn't guarantee thread safety. However, JCL can be safely used in a multi-threaded environment as long as the underlying implementation is thread-safe. + + It would be very unusual for a logging system to be thread unsafe. Certainly, JCL is thread safe when used with the distributed Log implementations. + + == How Can I Switch Logging Levels On And Off? == + + See How Do I Change The Logging System Configuration? + + == How Do I Change The Logging System Configuration? == + + The configuration supported by JCL is limited to choosing the underlying logging system. JCL does not (and will never) support changing the configuration of the wrapped logging system. Please use the mechanisms provided by the underlying logging system. == Log4JLogger does not implement Log == --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org