Return-Path: Delivered-To: apmail-jakarta-log4j-user-archive@apache.org Received: (qmail 44791 invoked from network); 21 May 2003 09:26:10 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 21 May 2003 09:26:09 -0000 Received: (qmail 19752 invoked by uid 97); 21 May 2003 09:28:27 -0000 Delivered-To: qmlist-jakarta-archive-log4j-user@nagoya.betaversion.org Received: (qmail 19745 invoked from network); 21 May 2003 09:28:26 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 21 May 2003 09:28:26 -0000 Received: (qmail 43508 invoked by uid 500); 21 May 2003 09:25:52 -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 43434 invoked from network); 21 May 2003 09:25:51 -0000 Received: from mail02.powweb.com (63.251.216.35) by daedalus.apache.org with SMTP; 21 May 2003 09:25:51 -0000 Received: from AVNER (unknown [213.8.45.193]) by mail02.powweb.com (Postfix) with ESMTP id 368B5E00D9 for ; Wed, 21 May 2003 02:26:01 -0700 (PDT) Message-ID: <06be01c31f85$6155a4e0$2400a8c0@kinor.corp> From: "Avner BenHanoch" To: "'Log4J Users List'" References: <5DABF7424840D411BE9600508B6621F80AD35BDB@exchukthis02.experian.co.uk> Subject: flush in Loggers Date: Wed, 21 May 2003 12:40:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I switch to log4j from a previous [internal] logging system. In our internal logging system I was able to call flush in order to force flush of log messages in case the application got critical error. Is this feature needed with log4j too? if yes, how to do it? thanks, Avner --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: log4j-user-help@jakarta.apache.org