Return-Path: Delivered-To: apmail-jakarta-log4j-user-archive@www.apache.org Received: (qmail 58086 invoked from network); 11 Nov 2003 20:42:31 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Nov 2003 20:42:31 -0000 Received: (qmail 51811 invoked by uid 500); 11 Nov 2003 20:42:15 -0000 Delivered-To: apmail-jakarta-log4j-user-archive@jakarta.apache.org Received: (qmail 51796 invoked by uid 500); 11 Nov 2003 20:42:15 -0000 Mailing-List: contact log4j-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@jakarta.apache.org Received: (qmail 51781 invoked from network); 11 Nov 2003 20:42:15 -0000 Received: from unknown (HELO mailhub2.bmwna.com) (207.16.209.148) by daedalus.apache.org with SMTP; 11 Nov 2003 20:42:15 -0000 Received: from szumail.uswl ([170.34.213.47]) by mailhub2.bmwna.com (NAVGW 2.5.2.21) with SMTP id M2003111115433301037 for ; Tue, 11 Nov 2003 15:43:35 -0500 Received: by SZUMAIL with Internet Mail Service (5.5.2657.72) id ; Tue, 11 Nov 2003 15:40:42 -0500 Message-ID: <70BBED1A2BBDD711A4340008C79188AF9A55EC@SZUMAIL> From: Ken.Liu@bmwna.com To: log4j-user@jakarta.apache.org Subject: RE: automatic reload Date: Tue, 11 Nov 2003 15:40:42 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > I don't know, perhaps my solution is too simplistic or too > low-tech, but for a webapp, I simply have a URL that I ping > when I change > the log4j config file. Since the config file doesn't change > automatically, This is the approach I use. I have a servlet that calls configure(). I also have it set up to accept a url parameter, in case I want to reload a log4j config file from a url (we developers don't always have access to the file system). > it's pretty trivial to hit the URL right after I change the > file. I agree, it's not fully automatic, but it certainly does avoid all the > rest of the headache with timers and threads. Agreed. I personally feel more confident when I can directly force the reload myself rather than waiting for some thread to silently reload the config. I guess I'm a control freak :) The login approach would work, but I don't personally see any benefit over the servlet approach. Ken --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: log4j-user-help@jakarta.apache.org