I imagine that you'll have problems because both of them will try to roll
the file.
FWIW, I'd discourage having multiple applications sharing the same log file.
There is no easy way to coordinate logging to a shared resource through
different vm's that I am aware of and you are likely to get unexpected
results in the file.
I use a shared directory but each application server writes to it's own
logfile, e.g. {machine_name}.log
-----Original Message-----
From: Rahul Kuchhal [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 13:06
To: [EMAIL PROTECTED]
Subject: Question about RollingFileAppender
Hi!, I have a question about RollingFileAppender. If
this is not the correct forum to ask this please
ignore this mail.
I have a application that runs on multiple machines.
All running instances of this application use a shared
file (kept on a shread UNC path) to initialize
themselves. The Log4J is also initialized at that time
and the log file name for RollingFileAppender is given
as a UNC full path. So the Log4j classes in all the
JVMs on different machines will try to write to the
same network location.
My question: is this supported by Log4J or only the
first JVM will be able to get the lock and write to
the file? Are there any problems with this
configuration?
Thanks in advance,
Rahul
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
---------------------------------------------------------------------
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]
