Return-Path: Delivered-To: apmail-jakarta-log4j-user-archive@apache.org Received: (qmail 33080 invoked from network); 30 Aug 2002 17:25:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 30 Aug 2002 17:25:48 -0000 Received: (qmail 15006 invoked by uid 97); 30 Aug 2002 17:26:04 -0000 Delivered-To: qmlist-jakarta-archive-log4j-user@jakarta.apache.org Received: (qmail 14897 invoked by uid 97); 30 Aug 2002 17:26:03 -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 14721 invoked by uid 98); 30 Aug 2002 17:26:01 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Subject: Re: UNIX file handler problem used up on log4j log files To: "Log4J Users List" X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Bin Yan" Date: Fri, 30 Aug 2002 13:25:56 -0400 X-MIMETrack: Serialize by Router on MailGate/Server/DOH(Release 5.0.10 |March 22, 2002) at 08/30/2002 01:26:00 PM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Agreed. Although I think the preferred solution is to "configure your logging at the server start" due to performance concerns. thx ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Tony Yan (Bin) BHNSM/DOH/NYS Tel: 518-473-1809 Email: bxy02@health.state.ny.us ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ = =20 Jin Zhao = =20 =20 > cc: = =20 Subject: Re: UNIX file = handler problem used up on log4j log files =20 08/30/2002 12:59 = =20 PM = =20 Please respond to = =20 "Log4J Users = =20 List" = =20 = =20 = =20 I guess so. Since you didn't close those file handles before another PropertyConfigurator call, they are accumulated with each servlet hit. = You can call Logger.shutdown after each session to see if it fixes the prob= lem. Alternatively, you may only need configure your logging at the server s= tart up instead of reconfiguring them at each servlet hit. A question to Ceki: Can the same problem happen to configureAndWatch() = ? Jin On Friday, August 30, 2002, at 10:45 AM, Bin Yan wrote: > We call the PropertyConfigurator each time a servlet is hit and MyLog= is > initiated. Maybe that's teh problem? > thx > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Tony Yan (Bin) > BHNSM/DOH/NYS > Tel: 518-473-1809 > Email: bxy02@health.state.ny.us > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > > > Ceki G=FClc=FC > > To: "Log4J Users= > List" > cc: > > 08/30/2002 11:41 Subject: Re: UNIX fil= e > handler problem used up on log4j log files > AM > > Please respond to > > "Log4J Users > > List" > > > > > > > -- To unsubscribe, e-mail: For additional commands, e-mail: = -- To unsubscribe, e-mail: For additional commands, e-mail: