logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 45236] Wriring output to an out-dated file.
Date Wed, 02 Jul 2008 23:47:18 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45236





--- Comment #7 from Thorbjørn Ravn Andersen <thorbjoern@gmail.com>  2008-07-02 16:47:17
PST ---
(In reply to comment #5)
> The behavior mentioned is consistent with configuring multiple instances of
> log4j writing to the same DailyRollingFileAppender.  The behavior and
> attachment suggests that the platform is a Unix and not Windows XP as reported.

The screen dump in the PDF strongly suggest to come from a Unix machine.  The
naming is consistent with the "Configuring Linux for the Installation of Oracle
Database 10g" document from Oracle

http://www.oracle.com/technology/obe/obe10gdb/install/linuxpreinst/linuxpreinst.htm

It is known that the DailyRollingFileAppender is not rolling over until an
event is logged which then triggers a check.  It would be consistent with known
behaviour if there were multiple log4j instances writing to the same files, so
one instance has rolled over but with others not having checked yet. I agree
with your findings.

As OC4J is mentioned in the screen dump it would be reasonable to expect that
we are dealing with the Oracle web container OC4J, and that the multiple
loggers could happen from two or more web applications with their own log4j
copy, but with the same log4j configuration.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message