https://issues.apache.org/bugzilla/show_bug.cgi?id=43867
--- Comment #43 from Thorbjørn Ravn Andersen <[EMAIL PROTECTED]> 2008-07-25 03:25:51 PST --- (In reply to comment #0) > After upgrading from 1.2.14 to 1.2.15 the following error show up during > shutdown: > log4j:ERROR LogMananger.repositorySelector was null likely due to error in > class > reloading, using NOPLoggerRepository. I suggest that the wording of this message (LogManager.java, line 177) is changed to something like. "log4j repository corrupted. Happens with some class loaders. Logging disabled. See https://issues.apache.org/bugzilla/show_bug.cgi?id=43867 for discussion" This is to help the person seeing this message as much as possible resolving the problem. The current message wording does not reflect the current consensus namely that this is essentially not a log4j problem. I would originally suggest adding an extra argument giving the requested stack trace, but thought better of it as it misleads more than it helps. -- 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]
