You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Andre Bogus (JIRA)" <ji...@apache.org> on 2013/09/27 13:14:02 UTC
[jira] [Comment Edited] (LOG4J2-392) Intermittent errors with
appenders
[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779803#comment-13779803 ]
Andre Bogus edited comment on LOG4J2-392 at 9/27/13 11:12 AM:
--------------------------------------------------------------
We appear to have the same problem using beta 9 with async appenders, however not all of our applications exhibit the same problem.
I will look into the culprits and try to find out what triggers the problem.
In the meantime, could someone with higher privileges in this issue tracker add 2.0-beta9 to the affected versions?
Update: The problem appears when using asynchronous loggers. The applications in question exit via thrown exception to the default VM exception handler. No log4j exception handler has been installed. Note that I cannot reproduce the problem using a small test application that only logs once and then throws an exception, so it appears that something else is amiss.
was (Author: llogiq):
We appear to have the same problem using beta 9 with async appenders, however not all of our applications exhibit the same problem.
I will look into the culprits and try to find out what triggers the problem.
In the meantime, could someone with higher privileges in this issue tracker add 2.0-beta9 to the affected versions?
> 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
> Environment: Windows 7 SP1 64bit
> Reporter: ilynaf
> Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org