[LOGGING-135] Thread-safety improvements

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.2
• Assignee: Unassigned
• Reporter: Sebb
• Created: 08/Feb/10 18:00
• Updated: 20/Mar/13 20:11
• Resolved: 20/Feb/13 12:31

Description

The LogKitLogger.logger field is not final or volatile so changes are not guaranteed to be published.
This includes calls to getLogger(), so two different threads using the same instance can theoretically both create the logger.