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=40025>. 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=40025 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO ------- Additional Comments From [EMAIL PROTECTED] 2006-07-12 16:52 ------- I don't see an obvious connection between the problem description and the stack traces. The only log4j related thing in the stack traces is a sleeping FileWatchdog waiting for changes to the configuration file do to a earlier call to configureAndWatch. Everything else seems to be related to object finalization. Could you modify your configuration code to call configure() instead and see if the problem still occurs. If it still does, could you see if it occurs when log4j is effectively disabled by a statement like: LogManager.getLoggerRepository().setThreshold(Level.OFF); -- 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]
