DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9506>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9506 Tool to debug appender duplications Summary: Tool to debug appender duplications Product: Log4j Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Appender AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The FAQ describes the typical causes of duplicate logging as due to duplicate appenders. However, there is no easy way to detect where the duplicate appenders are. It would be really nice if I could flip some kind of switch (ex: set some kind of environment variable) that would cause all appenders to announce themselves, and which loggers they are attached to. This would help me track down the offending appenders when I have duplicate log entries. The announcements could be part of the log record. This is similar to the C in the PatternLayout, except C doesn't include appender info, and only works if the configuration is read. If I have appenders that somehow get a Basic configuration, they won't dump out this info. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
