Imagine: Two processes own a file handle to the same file. I wonder that not
already the concurrent writing gives problems. But if one process wants to
rename the file, this can't become good in each case. (this is a OS and
Filesystem issue and not a Log4j issue).
If you want two JVM writing
You shouldn't have two JVM's writing to the same file. If you want
logs from 2 JVMs to go to the same file you can have them send out the
logs on a SocketAppender and have a ServerSocket(name?) receive them
and write them to the file.
On 6/28/06, Pavan Sara (CONS), IT [EMAIL PROTECTED] wrote:
ONE-ANS
email: [EMAIL PROTECTED]
===
-Original Message-
From: James Stauffer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 28, 2006 15:45
To: Log4J Users List
Subject: Re: Same configuration file for application running in different JVMs
You shouldn't
On 6/28/06, Pavan Sara (CONS), IT [EMAIL PROTECTED] wrote:
Thank you very much!
I'll try.
What about the second situation I described?
1) A single application
2) Two appenders writing on the same file (but
with different layout and level).
Is it not an acceptable configuration?
According to
