logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 40025] - Log4J causing Java application to hang
Date Wed, 12 Jul 2006 16:52:51 GMT
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


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From carnold@apache.org  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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message