Only thing I was able to figure out was to write an error handler so I could ensure I knew what was going on since log4j eats the exceptions.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 27, 2003 9:27 AM > To: [EMAIL PROTECTED] > Subject: What happens when log4j can't write? > > > I'm going to use log4j in a production environment, and it is > important for me to be sure that the logging is working. So, > if the logging stops (for whatever reason - let's say for > example, I'm logging to file and I run out of disk space), I > need to notify the operators so that they can take action. > What options do I have? Is there any way to configure my > logging in order to accomplish that? Any input will be appreciated. > > Serge A. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
