I'm using a RollingFileAppender on Solaris with Hotspot 1.5.  The disk
partition recently filled and my application hung.  The threads were alive,
but not processing input. Since log4j is the only function that writes to
the local disk, I'd like to know more about how it deals with this problem.


If a Logger tries to write, say with log.info("message") but the disk is
full, does the method just return immediately? If the method does not return
immediately, then can that be configured?

Thanks

Reply via email to