Return-Path: Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: (qmail 80567 invoked from network); 7 Feb 2006 12:02:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Feb 2006 12:02:53 -0000 Received: (qmail 20766 invoked by uid 500); 7 Feb 2006 12:01:55 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 19824 invoked by uid 500); 7 Feb 2006 12:01:52 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 19812 invoked by uid 99); 7 Feb 2006 12:01:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2006 04:01:51 -0800 X-ASF-Spam-Status: No, hits=0.9 required=10.0 tests=HTML_10_20,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of kernelkole@gmail.com designates 64.233.162.202 as permitted sender) Received: from [64.233.162.202] (HELO zproxy.gmail.com) (64.233.162.202) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2006 04:01:51 -0800 Received: by zproxy.gmail.com with SMTP id 40so1347742nzk for ; Tue, 07 Feb 2006 04:01:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=aaQBY9Ml+9NXoXXub9Zqr6sI5WrA/JNcQSmw7soLF5SAElgqzMPZJPAcnSABA8ecd5cG3pmyop5EbSsQ49KTUNVn9dLcf4sKopNK9qbzTy0Kn30iYcrLEuNGXWIx3gsqYkhyIVRzyPvPndxtKrQFYYTtWRYs/6edgdj4ztRp2wU= Received: by 10.64.10.9 with SMTP id 9mr385281qbj; Tue, 07 Feb 2006 04:01:30 -0800 (PST) Received: by 10.65.163.14 with HTTP; Tue, 7 Feb 2006 04:01:30 -0800 (PST) Message-ID: <96d4ad0b0602070401u336c8f50pb9821ffb9364c043@mail.gmail.com> Date: Tue, 7 Feb 2006 06:01:30 -0600 From: kameron cole To: log4j-user@logging.apache.org Subject: where do you put the log4j.properties in J2EE? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_133_3293927.1139313690110" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_133_3293927.1139313690110 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I've searched wide for the answer of where to put the log4j.properties file in a J2EE system. It's kind of sad to me that none of the articles begins to address this really essential part of the set up. in one obscure post, someone said a "quick fix" was to put it in one of the extension classloader folders for the various appservers. can't really be = a good thing, since it would affect everybody else's log4j. still, it does work. so, it's not a problem that I don't understand the classpath - it's that log4j looks somewhere, not everywhere, for a file called log4j.properties. someone must know that exact place where the log4j designers intended to pu= t that file. thank you for any and all answers. -- yours, k. ------=_Part_133_3293927.1139313690110--