https://issues.apache.org/bugzilla/show_bug.cgi?id=43867
--- Comment #53 from Curt Arnold <[EMAIL PROTECTED]> 2008-08-05 14:39:22 PST --- For comment #50: The only place that we know where it happens is within clearReferences, but we can't say that is the only place that it happens. We can tell Tomcat users to turn off clear references since it is an unsafe optimization, but apparently it is a very desirable optimization (otherwise it wouldn't be the default and they wouldn't have gone to the trouble to write it). For some class of users, they have observed that they upgrade to log4j 1.2.15 and now they get a message that they didn't get before and think that it is a log4j issue. They never say the NPE that motivated writing the NOPLoggerRepo and the message. For those that did see the NPE, log4j 1.2.15 was a good upgrade, those that never say the NPE and now see the message see it as a problematic upgrade. The problem is a latent Tomcat issue, but they don't know that and for us to tell them to change their configuration might be enough to discourage them from keeping current, so now we have pressure to try to continue to support 1.2.14 or whatever that for some reason we don't understand doesn't exhibit the issue for them (but NPE's for others). The belt and suspenders approach (message with a FAQ and lowering level where we think it is innocuous) seems best to me, but I'll commit them as two separate changes (FAQ first) and we can decide whether to keep one or the other or both. -- 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]
