So files officially are not supported for interleaving logging? I'm trying to check the FAQs, but the log4j site seems to be down. I've been running in this setup for over a year and never ran into any issues until recently. What is the underlying reason for not supporting this functionality? Does this only afflict the rolling appender?
-----Original Message----- From: James Stauffer [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 02, 2006 11:09 AM To: Log4J Users List Subject: Re: quiet writer throws runtime exception Write to something the works with multiple servers (database, queue, socket, etc) or write to a file that is dictinct on each server. On 5/2/06, Evans, Jess <[EMAIL PROTECTED]> wrote: > Hello all, > > I'm receiving these errors in our production system. We have two app. > server instances running in a cluster. It seems to occur some nights > after midnight, which suggests an issue with rolling. It occurs > randomly and on one instance only. Once it starts, every call to log4j > in that container fails with an identical error. > > I believe someone stated that log4j doesn't support multiple JVMs > interleaving to a single log file. Is this correct? If so, what is the > suggested configuration to allow clustered application server instances > to log to individual files (without having to support a distinct log4j > configuration per instance). -- James Stauffer Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- 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]
