If I have many processes across multiple hosts (possibly across multiple timezones) logging to the same file using the method above, what happens to timestamps?
The timestamp is created when the logging event is created. That is so say, when the debug, info, warn, error or fatal method is invoked. This is unaffected by the time at which they may arrive at a remote socket server. Since the timestamps are stored in UTC format inside the event, they all appear in the same timezone as the host creating the logfile. Since the clocks of various machines may not be synchronized, this may account for time interval inconsistencies between events generated on different hosts. While this is the intended behavior, it only recently became so due to a bug discovery between version 1.0.4 and 1.1b1. Versions 1.0.4 and before had their timestamp regenerated in the converter. In this case the timestamps seen in the log file would all appear in order, generated at the time they arrived at the log server host according to its local clock. Why should I donate my extensions to log4j back to the project? Contrary to the GNU Public License (GPL) the Apache Public Lic
Related Questions
- If I have many processes across multiple hosts (possibly across multiple time zones) logging to the same file using the RemotingAppender, what happens to timestamps?
- If I have many processes across multiple hosts (possibly across multiple time zones) logging to the same file using the method above, what happens to timestamps?
- How about the timesamps of events generated by multiple processes across multiple hosts (possibly across multiple timezones)?
