[LOG4NET-323] AbsoluteTimeDateFormatter caches string representation of now too aggressively

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.11
• Fix Version/s: 1.2.12
• Component/s: Other
• Labels: datetime formatter, layout
• Assignee: Unassigned
• Reporter: Matthew Gabeler-Lee
• Created: 09/Feb/12 20:01
• Updated: 05/Mar/12 19:39
• Resolved: 05/Mar/12 19:39

Description

The AbsoluteTimeDateFormatter class caches the string representation of the most recent timestamp it has seen, down to the second.

The problem is, this cache is inherited by other formatter classes, which represent that value in different ways.

This causes the formatted date/time generated by layouts and thus appended to logs to be inconsistent if there are multiple date/time formats in use in different appenders. For example, I have a debug appender which uses the %date

{ABSOLUTE}

format, and a log file appender which uses the %date

{ISO8601}

format. Because the debug appender sees most messages first, most (but not all!) entries in the log file get the ABSOLUTE format, even though ISO8601 was specified.

The cache of the string representation needs to be specific to a particular date format.