> But I finally decided as I was upgrading Tomcat that I'd address that
> problem by moving to a rolling file appender. Seems to me that I have
> two choices for doing this:
we find the rolling file appenders useful as you can specify periodcity and
they rename themselves to dated filenames. you can then manage those files
however you like.
> a) Convert my log4j.properties file to use a RollingFileAppender. I
> did this, and much to my surprise the log files showed up in my
> %WIN_HOME%/system32 folder.
we put a placeholder in the log4j.properties file ${log4j.home} that gets
replaced with Ant when the build task is called either for development or
production. That means we have separate properties files for dev and prod
configs and the log4j.home parameter is actually a full path. You could adapt
this to your own scenarios. I've never gotten by default the log4j file logs
into tomcat's logs either, so use this other method.
> b) Leave my log4j.properties file using ConsoleAppender and use a
> <Logger> element in my <Context> to have Tomcat put the output into a
> file. I have not tried this yet, and wanted to post this query before
> digging further into it. Is this a good alternative? I have two
> issues with it:
Yeah probably not a good logging stategy considering it's gone ;) And anyways,
that stuff was only for specific types of logging info that will now come
through in stdout.
Allistair.
<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com";>www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
