If I recall there was a sequence number added to loggingevent in the 1.3 codebase, but that was taken out a while ago.
You can modify logging events before they're processed by appenders by using the org.apache.log4j.rewrite package in the 'receivers' companion. Create your own rewritepolicy implementation which adds a sequence number property to each loggingevent, and then specify a rewriteappender which references your rewritepolicy implementation and delegates to a regular appender. http://logging.apache.org/log4j/companions/receivers/apidocs/index.html http://svn.apache.org/viewvc/logging/log4j/companions/receivers/trunk/src/main/java/org/apache/log4j/rewrite/ Scott Deboy COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax: 503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -----Original Message----- From: Paul Duffy [mailto:[EMAIL PROTECTED] Sent: Wed 12/5/2007 7:29 PM To: Log4J Users List Subject: Sequence numbers for LoggingEvents Folks, I have an application that is likely to produce LoggingEvents on identical millisecond epochs. Thus I also need a sequence number to unambiguously determine event order. Is there any facility by which I can also include a montonically increasing sequence number in the event? I went back through the archives...seems some work was started here for 1.3, but was stopped? Cheers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
