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=35324>. 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=35324 Summary: Stacktrace may choke on null fields, as org.apache.log4j.spi.ThrowableInformation.VectorWriter.p rintln(null) will bomb Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Appender AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] VectorWriter extends java.io.PrintWriter but it does not suppply its forgiving services when trying to println(null). Each of Sun's implementations of println (Object) is capable of handling the singular case of Object==null gracefully, but ThrowableInformation.VectorWriter does not, which effectively breaks custom made printStackTrace methods at the very instant, when the stack trace is to be output to a logger. In detail, org.apache.log4j.spi.ThrowableInformation.VectorWriter.println (Object) looks as follows: public void println(Object o) { v.addElement(o.toString()); } whilst it might preferrably be: public void println(Object o) { v.addElement(String.valueOf(o)); } -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
