Re: log4j and log file lock?
- From: Owen Jacobson <angrybaldguy@xxxxxxxxx>
- Date: Wed, 15 Aug 2007 15:20:42 -0700
On Aug 15, 2:25 pm, alejandrina <apat...@xxxxxxxxx> wrote:
Hi all,
We have a processor farm (currently 8 machines) running the same
application with different input parameters. We use log4j to record
interesting stuff; we'd like to use a single log file in a networked
disk. We noticed that the 8 machines are trampling on each other as
they write to the log file (symptoms are nulls embedded in messages,
incomplete messages, duplicate messages....). I have assumed that this
is because access to the log file is not "locked" (using something
like Java's FileLock API).
Is there a solution to this problem? Thread syncronization is not an
option, of course, as these are different computers.
Thanks for any ideas,
Alejandrina
Use the syslog appender and let a single network-available syslog
instance handle the actual log files.
-Owen
.
- References:
- log4j and log file lock?
- From: alejandrina
- log4j and log file lock?
- Prev by Date: Re: Simple example for fomatting output in columns?
- Next by Date: Re: Transgressing the Boundaries: Towards a Transformative Hermeneutics of Copyright and Patent Law?
- Previous by thread: log4j and log file lock?
- Next by thread: Re: log4j and log file lock?
- Index(es):
Relevant Pages
|
|