If anyone cares, this is solved. It was just a version conflict between
two 3rd party jars in my application.

On 06/15/2006 04:44 PM, Rohnny Moland wrote:
> Hi,
> 
> I am struggling with this exception that comes about 10 seconds after
> I have started my application:
> 
> log4j:ERROR Could not close
> [EMAIL PROTECTED]
> java.io.IOException: Bad file descriptor
>       at java.io.FileOutputStream.close0(Native Method)
>       at java.io.FileOutputStream.close(FileOutputStream.java:279)
>       at sun.nio.cs.StreamEncoder$CharsetSE.implClose(StreamEncoder.java:431)
>       at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:160)
>       at java.io.OutputStreamWriter.close(OutputStreamWriter.java:222)
>       at java.io.FilterWriter.close(FilterWriter.java:92)
>       at org.apache.log4j.FileAppender.closeFile(FileAppender.java:183)
>       at org.apache.log4j.FileAppender.reset(FileAppender.java:338)
>       at org.apache.log4j.WriterAppender.close(WriterAppender.java:204)
>       at org.apache.log4j.AppenderSkeleton.finalize(AppenderSkeleton.java:124)
>       at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
>       at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
>       at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
>       at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
> 
> ..and after that log4j stops to work and even system.out does not
> work. Just wonder what the reason could be for that.
> 
> The log4j configuration stuff should be properly setup. Could it be a
> weak reference somewhere, but how can I know where..
> 
> Using log4j 1.2.13, SuSE 64/x86 10.1 and java 1.5_07 64bit.
> 
> 
> Thanks in advance,
> Rohnny
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to