https://issues.apache.org/bugzilla/show_bug.cgi?id=43867
--- Comment #19 from Dan Armbrust <[EMAIL PROTECTED]> 2008-07-07 07:48:18 PST --- I don't know what more info you possibly need. This entire problem is well documented already. See Comment #8. Comment #11, and Comment #10 (from a Tomcat guy) The quick summary is that log4j started logging more errors than it used to from 1.2.14 to 1.2.15. Now, when it is deployed in a webapp in tomcat which is stopped, it logs ugly null pointer exceptions - as errors - which end up on the tomcat console. The real problem is caused by how tomcat does its shutdown process, which may or may not be fixed at present. The referenced Tomcat bug seems to indicate that it now may be fixed, without the workaround presented in comment #10. But to fix the log4j issue, and keep ugly errors from happening, what I think should happen is that Suggestion 5 from Comment #8 should be implemented in log4j. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
