[LOGCXX-194] Garbage in log files when appenders are defined in multiple levels of the logger hierarchy

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Fix Version/s: 0.10.0
• Component/s: Appender
• Assignee: Curt Arnold
• Reporter: Myles Bunbury
• Created: 01/Oct/07 17:23
• Updated: 23/Oct/07 20:42
• Resolved: 23/Oct/07 20:42

Description

When appenders are defined in multiple levels of the logger hierarchy, corruption of the log output occurs.

To illustrate, create a log4cxx.properties file wih the following loggers defined:

log4j.rootLogger=debug, apndr1
log4j.logger.subLogger=debug, apndr2

'apndr1' and 'apndr2' can be any type of appender, although for the purposes of investigating this bug, FileAppenders and RollingFileAppenders were used with PatternLayout and XMLLayout layouts.

Once configured, using multiple threads to create a heavy load on the logging system, send log events to the 'subLogger' logger.

Some of the data in the resulting logging output will include garbage.

Issue Links

• duplicates: LOGCXX-175 APRCharsetEncoder is not thread safe
• relates to: LOGCXX-186 Garbage characters in log files when log requests from multiple threads with hyperthreading enabled