You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Ole Bulbuk <Ol...@ebp.de> on 2003/05/19 15:59:37 UTC

IOException in Category.error()

Hi,

when the underlying disk is full (which will happen quite frequently for our
software), Category.error(...) throws an Exception:
log4j:ERROR Failed to flush writer,
java.io.IOException: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java(Compiled
Code))
	at
sun.nio.cs.StreamEncoder$ConverterSE.implFlush(StreamEncoder.java(Compiled
Code))
	at
sun.nio.cs.StreamEncoder$ConverterSE.implFlush(StreamEncoder.java(Compiled
Code))
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java(Compiled
Code))
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java(Compiled
Code))
	at
org.apache.log4j.WriterAppender.subAppend(WriterAppender.java(Compiled
Code))
	at
org.apache.log4j.WriterAppender.subAppend(WriterAppender.java(Compiled
Code))
	at
org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:225)
	at
org.apache.log4j.WriterAppender.append(WriterAppender.java(Compiled Code))
	at
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java(Compiled
Code))
	at
org.apache.log4j.BufferAppender.append(BufferAppender.java(Compiled Code))
	at
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java(Compiled
Code))
	at
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(Unknow
n Source)
	at org.apache.log4j.Category.callAppenders(Unknown Source)
	at org.apache.log4j.Category.forcedLog(Unknown Source)
	at org.apache.log4j.Category.error(Unknown Source)
	at
org.apache.avalon.framework.logger.Log4JLogger2.error(Log4JLogger2.java:145)
	at
de.ebp.globus.messageoutput.OutputProducerComp$1.execute(OutputProducerComp.
java(Compiled Code))
	at
de.ebp.workerpool.ThreadMultiplexer$ComponentThread.run(ThreadMultiplexer.ja
va:66)

I think this is a undesired reaction. An error in an error handling system
(like logging) is usually something really bad. It would be nice if the log
message would have been written to standard error (System.err) instead.

Regards,

Ole

P.S.: We are using Log4J 1.2.6
-- 
Ernst Basler + Partner GmbH
Tuchmacherstraße 47
14482 Potsdam
Tel: (0331) 74 75 9-0
Direkt: (0331) 74 75 9-60
Fax: (0331) 74 75 9-90

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