Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 57550 invoked from network); 18 Feb 2005 14:17:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 18 Feb 2005 14:17:29 -0000 Received: (qmail 2805 invoked by uid 500); 18 Feb 2005 14:17:25 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 2723 invoked by uid 500); 18 Feb 2005 14:17:25 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: 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 2710 invoked by uid 99); 18 Feb 2005 14:17:25 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from gulcu002.worldcom.ch (HELO mail.qos.ch) (212.74.184.210) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 18 Feb 2005 06:17:23 -0800 Received: from kal.qos.ch (kal [192.168.1.3]) by mail.qos.ch (Postfix) with ESMTP id 53C381EC077 for ; Fri, 18 Feb 2005 15:26:24 +0100 (CET) Message-Id: <6.0.3.0.0.20050218150007.01fdfea0@mail.qos.ch> X-Sender: ceki@mail.qos.ch (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Fri, 18 Feb 2005 15:18:48 +0100 To: "Jakarta Commons Developers List" From: Ceki =?iso-8859-1?Q?G=FClc=FC?= Subject: Re: jcl blog post In-Reply-To: References: <6.0.3.0.0.20050217152311.03cd55c8@mail.qos.ch> <6.0.3.0.0.20050217163005.03cf2a48@mail.qos.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Vic, The defects can be reproduced easily. Assuming you deployed your application on Tomcat, the combination known to= =20 work safely is: 1) Leave the file TOMCAT_HOME/bin/commons-logging-api.jar as is. 2) Place the files commons-logging.jar and log4j.jar in the directory=20 TOMCAT_HOME/commons/lib/. 3) Do not include any other copies of commons-logging.jar and log4j.jar in= =20 your web-applications' WEB-INF/lib/ directory. 4) Do not set the org.apache.commons.logging.LogFactory property. Was your deployment combination different from the above? At 02:54 PM 2/18/2005, Vic wrote: >I used to use both together. For what ever reason, I have stress tested=20 >and put in production several systems, one with 10,000 concurrent users,=20 >one w/ 40,000 concurrent users... and everything seems to be working. I=20 >was not aware of any bugs. > >Now .... I use WebStart so likely at least a part will be JDK logging. >.V > >Ceki G=FClc=FC wrote: > >> a problem with JCL, a totally defective piece of >>software, which makes life very difficult, if not impossible, for >>log4j users. --=20 Ceki G=FClc=FC The complete log4j manual: http://www.qos.ch/log4j/ --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org