https://issues.apache.org/bugzilla/show_bug.cgi?id=43867
--- Comment #48 from Curt Arnold <[EMAIL PROTECTED]> 2008-08-05 13:46:32 PST --- I'm not sure how to interpret message #47. Maybe best for me to take a shot at a fix and then for you to critique it. We know one situation that can result in the NOPLoggerRepository warning, the undesirable reloading and reinitialization of classes in WebappClassLoader.clearReferences. As that scenario is described, it seems like there is little potential for resource leakage or other issue that should concern a site admin, so the message could be dropped to a LogLog.debug() or similar which would likely be suppressed. However, we can't say that all situations that can result in the NOPLoggerRepository are as innocuous. So we don't want to lower the severity in situations where we can't identify. In those cases, we've got an obligation to let the admin know that log4j has a serious problem and can't perform as would be expected. Maybe sometimes the NOPLoggerRepo message does occur because of misconfiguration or unterminated threads, if those cases occur, we shouldn't hide the info from the admin. Comment #38 touched on the need to not hide problems from admins that might let them know that things are going south. There is a compromise here and it won't be perfect, however hopefully we could eliminate a lot of unnecessarily scary messages to Tomcat admins that don't reflect a potential stability issue while still informing other uses when we feel that our stability has been compromised. -- 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]
