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 51027] Stuck Thread due to lock contention with RollingFileAppender
Date Thu, 07 Apr 2011 05:02:50 GMT

Curt Arnold <carnold@apache.org> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Curt Arnold <carnold@apache.org> 2011-04-07 01:02:47 EDT ---
Support questions should go on log4j-users@apache.org.  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

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

View raw message