This has been added to the wrong issue list but I would like you folks to see it.
---------- Forwarded message ---------- From: <[email protected]> Date: Wed, Jul 31, 2013 at 10:25 AM Subject: [Bug 41214] Deadlock with RollingFileAppender To: [email protected] https://issues.apache.org/bugzilla/show_bug.cgi?id=41214 --- Comment #54 from [email protected] --- I upgraded to log4j2 and still it was jamming up for ten to twenty seconds, directly after midnight when rollover and compression happens. One thread is java.lang.Thread.State: RUNNABLE at java.io.RandomAccessFile.writeBytes(Native Method) at java.io.RandomAccessFile.write(RandomAccessFile.java:499) at org.apache.logging.log4j.core.appender.rolling.FastRollingFileManager.flush(FastRollingFileManager.java:105) at org.apache.logging.log4j.core.appender.rolling.FastRollingFileManager.write(FastRollingFileManager.java:89) - locked <0x00000000e81ae1e0> (a org.apache.logging.log4j.core.appender.rolling.FastRollingFileManager) at org.apache.logging.log4j.core.appender.OutputStreamManager.write(OutputStreamManager.java:129) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:115) at org.apache.logging.log4j.core.appender.FastRollingFileAppender.append(FastRollingFileAppender.java:97) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:102) at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:426) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:407) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:410) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:368) at org.apache.logging.log4j.core.Logger.log(Logger.java:110) at org.apache.logging.log4j.spi.AbstractLoggerWrapper.log(AbstractLoggerWrapper.java:55) at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:984) and then scores of other threads at java.lang.Thread.State: BLOCKED (on object monitor) at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.checkRollover(RollingFileManager.java:108) - waiting to lock <0x00000000e81ae1e0> (a org.apache.logging.log4j.core.appender.rolling.FastRollingFileManager) at org.apache.logging.log4j.core.appender.FastRollingFileAppender.append(FastRollingFileAppender.java:88) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:102) at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:426) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:407) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:410) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:368) at org.apache.logging.log4j.core.Logger.log(Logger.java:110) at org.apache.logging.log4j.spi.AbstractLoggerWrapper.log(AbstractLoggerWrapper.java:55) at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:984) Changing to disruptor fixed the problem (async appenders might have fixed the problem too i suspect). -- 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] -- http://www.grobmeier.de https://www.timeandbill.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
