https://issues.apache.org/bugzilla/show_bug.cgi?id=41214
--- Comment #27 from Mohit Khanna <[email protected]> 2009-04-22 05:53:07 PST --- Hi All, I wanted to add more data points on behalf of Vijay (post #26) above. 1. The disk space on the partition to which the logs are written was 100% full at some point in time on the server. Though we have not tried to reproduce it this way yet, but needed some confirmation on Log4J behavior under this condition. We are not even sure whether disk full can cause this issue. Could this have caused the deadlock? How does Log4J behave upon a disk full condition? 2. As per the stack trace thread (EventListenerThreadPool:Thread-1087) had encountered an uncaught-exception. We are not yet sure what this exception was, BUT sadly that same call/thread 'deadlocked' and no logs (diskfull?) got dumped. . . at java.io.PrintStream.print(Unknown Source) at java.lang.ThreadGroup.uncaughtException(Unknown Source) at java.lang.ThreadGroup.uncaughtException(Unknown Source) at java.lang.Thread.dispatchUncaughtException(Unknown Source) I am not sure whether this is a known issue/behavior in Log4J. But wanted to understand how we could resolve this. Will upgrading to Log4J 1.2.15 help? 1.2.14 did have deadlock fixes for AsyncAppender, but RollingFileAppender also seem to have the same bug. -- 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]
