Return-Path: 
 <log4j-user-return-10434-qmlist-jakarta-archive-log4j-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-log4j-user-archive@apache.org
Received: (qmail 16865 invoked from network); 11 Aug 2003 13:10:17 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 11 Aug 2003 13:10:17 -0000
Received: (qmail 8669 invoked by uid 97); 11 Aug 2003 13:12:57 -0000
Delivered-To: qmlist-jakarta-archive-log4j-user@nagoya.betaversion.org
Received: (qmail 8662 invoked from network); 11 Aug 2003 13:12:57 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 11 Aug 2003 13:12:57 -0000
Received: (qmail 15314 invoked by uid 500); 11 Aug 2003 13:09:53 -0000
Mailing-List: contact log4j-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:log4j-user-subscribe@jakarta.apache.org>
List-Help: <mailto:log4j-user-help@jakarta.apache.org>
List-Post: <mailto:log4j-user@jakarta.apache.org>
List-Id: "Log4J Users List" <log4j-user.jakarta.apache.org>
Reply-To: "Log4J Users List" <log4j-user@jakarta.apache.org>
Delivered-To: mailing list log4j-user@jakarta.apache.org
Received: (qmail 15111 invoked from network); 11 Aug 2003 13:09:50 -0000
Received: from viap100.atea.be (HELO hrtades9.atea.be) (194.78.143.100)
  by daedalus.apache.org with SMTP; 11 Aug 2003 13:09:50 -0000
Received: from hrtades10.atea.be (siemens.atea.be [139.10.143.141]) by
 hrtades9.atea.be with SMTP (Microsoft Exchange Internet Mail Service Version
 5.5.2653.13)
	id Q3BKYRKC; Mon, 11 Aug 2003 15:09:47 +0200
Received: by siemens.atea.be with Internet Mail Service (5.5.2653.19)
	id <Q3B1B418>; Mon, 11 Aug 2003 15:09:47 +0200
Message-ID: <57FD2C3A246F76438CA6FDAD8FE9F195719768@hrtades7.atea.be>
From: Hancke Patrick <Patrick.Hancke@siemens.com>
To: "'log4j-user@jakarta.apache.org'" <log4j-user@jakarta.apache.org>
Subject: log4j: dump wrap-around buffer of all log messages
Date: Mon, 11 Aug 2003 15:09:44 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Dear log4j users,


Currently I'm evaluating log4j 1.2.8 to replace an other Java Trace package
(see http://visibleworkings.com/trace/) in our applications. Log4j's big
advantage is its performance, but still I'm missing a feature that is
present in the Java Trace package: the ability to dump a wrap-around buffer
of, let's say, the last 500 log messages in the log file.

The wrap-around buffer (think of it as an array of let's say 500 log
messages) contains at any moment, the last 500 log messages. The idea is
that the logger has 2 log levels: one which determines what level is present
in the log file (or std out or whatever), another which determines at what
level the internal wrap-around buffer is filled with messages. This way, it
is possible to let your application log at level INFO, while the internal
buffer keeps all messages of level DEBUG or higher. When an exception is
thrown, the user should have the ability to request a dump of the buffer,
such that the more detailed DEBUG messages are also present in the log file
to make debugging more easy.

Is this possible in log4j? If not, has anyone a workaround for this or
should I ask for a feature request?


Kind regards,
Patrick Hancke
Siemens Atea IC D BS PD2
tel ++32(0)14 - 25 24 27
fax ++32(0)14 - 25 30 25

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org