Guten Tag Alder Netw, am Dienstag, 13. Mai 2014 um 02:06 schrieben Sie: > OK, we would love to use the existing Log4cxx buffering mechanism, > but we found the time-stamp appended by Log4Cxx is the dequeue time > rather than the enqueue time, so the question becomes is there any > control over using the original log generating time instead of the delivery > time?
As I said before, no, not unless you re-implement the logging macros and override the classes Logger and LoggingEvent on your own to be able to provide a custom timestamp. What do you mean with "dequeue time"? The timestamp used by Log4cxx is directly after constructing the log message and therefore very close to the time when the caller issued a log message, there's no buffering or queuing in use there. Buffers, caches and such may only be used afterwards using appenders, but at that moment the timestamp for the log statement issued is already fixed. Have a look at logger.cpp forcedLog, that's being called from the macros. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
