You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2006/12/16 01:11:33 UTC

DO NOT REPLY [Bug 41186] - AsyncAppender in 1.2.14 DiscardSummary events create NullPointerExceptions in layouts

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41186>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41186


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From carnold@apache.org  2006-12-15 16:11 -------
Committed rev 487725 on trunk, 487224 on 1.2 branch.  Passing null for the fully qualified category (aka 
logger) name in the LoggingEvent constructor would cause a NPE in the 1.2 code base, but not 1.3.  
Addressed problem by passing in a string that should not match any class name in a stack trace which 
should result in the class name and location being reported as "?" in both branches.

Added tests to both test suites.  Surprised that very few of the AsyncAppender tests had been ported back 
to log4j 1.2, but only backported essential support classes.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org