Re: Access logfile logger

Hi Jason, What are your requirements for "reporting functions"? Do you need to discover statistics about the current log file? I'm guessing, but it seems that the most useful statistic might be the current size of the log file. I've outlined a possible way you might be able to get at that.

logging issue in application installed on clustered Weblogic Server

HiWe have any application which is installed on a clustered Weblogic server, there are 3 clusters on which this application is installed, All the logs written by startup servlet are written to both A1 and STDOUT appender, but then once the application is running logs are written to STDOUT only Ho

RE: Call for feedback

Hi Thorbjørn, Thanks for your comment. In simple terms, what we do for making these logs tamper-evident is to process each line and then chain-hashing them. This means that any tampering in any record (even a single byte in one record) equals to an interruption in the hash chain, which allow us

AW: Access logfile logger

You cannot get access to the file object itself for reading purpose because the FileAppender uses a FileWriter class for writing to the file. But you can learn the file name where the appender writes to. Not each logger instance which you get by Logger.getLogger() has appenders attached. Only th

Re: Access logfile logger

I think the approach should be via the appender. you can try and extend it - AFAIK only the appender can give you the file name. On Mon, May 4, 2009 at 3:56 PM, wrote: > Hi, > > I'm using log4j with a DailyRollingFileAppender. Now I want to add some > reporting functions to the same application

Access logfile logger

Hi, I'm using log4j with a DailyRollingFileAppender. Now I want to add some reporting functions to the same application that uses this appender. So I need to get access to the logfile that is written by the file appender. Only the current logfile needs to be read so is is possible via the logge

AW: [SPAM (Bayesain Analysis)] - Log file per thread - Bayesian Filter detected spam

Log4j distinguishes between Loggers and Appenders for a good reason: - Loggers define WHAT is logged (level, source) - Appenders define WHERE the log statement goes (console, file, etc.) and how it is formatted You want to have a new file for each new thread, so this is an appender issue whic