https://issues.apache.org/bugzilla/show_bug.cgi?id=51027
Curt Arnold <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Curt Arnold <[email protected]> 2011-04-07 01:02:47 EDT --- Support questions should go on [email protected]. There may be a bug in there, but there is not enough to determine what it is or where it lies. Your thread dump was truncated. The thread stack that was shown is expected when another thread is in the process of logging. What is needed is to see the stack trace on the other thread which apparently holds a lock on logger. If there is a call inversion, there could be a deadlock. In addition, it is always good to report the version of log4j in use and whether the behavior occurs with the current release version and extra points if the current SVN head is tested. Operating system and JVM can also be helpful. Marking as invalid, please post again on log4j-user with more info. -- 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]
