logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andre Bogus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-392) Intermittent errors with appenders
Date Thu, 06 Feb 2014 16:10:17 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893486#comment-13893486

Andre Bogus commented on LOG4J2-392:

Hi Remko,

I just built HEAD and tested the AppenderOverwhelmer again. This indeed removes the AppenderRuntimeException.
However, running the AppenderOverwhelmer gets out only 3.047 of 10.000 messages to stdout
on my machine before exiting with only a number of status debug messages.

In my very humble opinion, this change makes it worse, not better. Before there was at least
an error that implied that messages had not been written out. Now they are silently discarded.
Ok, I get it, don't use async loggers for anything that should be logged under all circumstances,
but adding a status error method if logs are being discarded, even better combined with a
grace period (perhaps only if there are log messages waiting in the ring buffer) for async
loggers would be really helpful.

Please suggest how you want to go forward. If you like, I can close the bug and open a new
one describing the behavior I discussed above.


> Intermittent errors with appenders
> ----------------------------------
>                 Key: LOG4J2-392
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-392
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.0-beta8, 2.0-beta9
>         Environment: Windows 7 SP1 64bit
>            Reporter: ilynaf
>            Assignee: Remko Popma
>             Fix For: 2.0-rc1
>         Attachments: AppenderOverwhelmer.java, Log4J2.zip, log4j2.xml
> I intermittently receive following errors after upgrading to beta 8. EVERYTHING was working
well with beta 6:
> * 1st error (happens most frequently)
> 2013-09-05 10:48:37,722 ERROR Attempted to append to non-started appender LogFile
> * 2nd error:
> 2013-09-05 10:49:38,268 ERROR Attempted to append to non-started appender LogFile
> 2013-09-05 10:49:38,268 ERROR Unable to write to stream log/ui-selenium-tests.log for
appender LogFile
> 2013-09-05 10:49:38,269 ERROR An exception occurred processing Appender LogFile org.apache.logging.log4j.core.appender.AppenderRuntimeException:
Error writing to RandomAccessFile log/ui-selenium-tests.log
> 	at org.apache.logging.log4j.core.appender.rolling.FastRollingFileManager.flush(FastRollingFileManager.java:108)
> 	at org.apache.logging.log4j.core.appender.rolling.FastRollingFileManager.write(FastRollingFileManager.java:89)
> 	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.appender.AsyncAppender$AsyncThread.run(AsyncAppender.java:228)
> Caused by: java.io.IOException: Write error
> 	at java.io.RandomAccessFile.writeBytes(Native Method)
> 	at java.io.RandomAccessFile.write(Unknown Source)
> 	at org.apache.logging.log4j.core.appender.rolling.FastRollingFileManager.flush(FastRollingFileManager.java:105)
> 	... 6 more

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message