I have experienced the same problem. I ended up having to write a new
FileAppender which checks every time the appender is written to wether
or not the logfile still exists. If it doesn't, I just open a new file
with the same name by calling setFile().
If I overlooked an easier or more logical
would have to do, could you tell me where
FileAppender writes to the file ? or wherever you added your code to
check if the file exists ?
Thanks in advance,
Regis
-Original Message-
From: MALLER Stijn (BMB) [mailto:Stijn.MALLER;proximus.net]
Sent: Thursday, October 24, 2002 3:05 PM
To: Log4J
Of course that is possible. Just put filters on your logstatements...
Like this:
appender name=FILE class=org.apache.log4j.FileAppender
param name=File value=debug_and_info.log/
param name=DatePattern value=_MMdd_HHmm/
layout class=org.apache.log4j.PatternLayout
Hi all,
I've posted this once before but received no answers...so here's another
try
I created a new Appender which extends the FileAppender. One of the
additional functionalities of this Appender should be the recreation of
a logfile when it has inadvertantly been deleted. (because at the
Hi everyone,
I've written an alternative DailyRollingFileAppender which simulates the
behavior of an old logger used in our company. There's one last
functionality that is lacking and I was wondering if anyone could help
me out or at least point me in the right direction.
At the moment the
Can you send your log4j.properties and your wrapper.properties?
This looks like a simple case of removing the consoleappender
-Original Message-
From: Qian Song [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 01, 2002 4:47 PM
To: [EMAIL PROTECTED]
Subject: How to disable tomcat's
See, just as I thought
You have the console appender attached. So if you want your
logstatements to occur only in the logfile (=log4j logfile) and not on
the console (=tomcat logfile) simply remove the console appender
1) Leave wrapper.properties remains unchanged
2) In log4j.properties
