Page History

F1.File indicates where you want your rolling file appender to be stored on your workstation (e.g., c:/dev/logs/oasskeleton.log)

log4j.rootLogger indicates the level of logging (e.g., INFO - see other levels in chart below) and where to send the log (e.g., C1 for the console and F1 for your rolling file appender):

 log4j.appender.F1=org.apache.log4j.RollingFileAppender

# We run in:   ORACLE_HOME/j2ee/home
# We write to: ORACLE_HOME/log/<logName>.log
log4j.appender.F1.File=c:/dev/logs/oasskeleton.log
log4j.appender.F1.MaxFileSize=10000KB
log4j.appender.F1.MaxBackupIndex=10
log4j.appender.F1.layout=org.apache.log4j.PatternLayout
log4j.appender.F1.layout.ConversionPattern=%d %p %c.%M - %m%n

# C1 goes to the console (for easier eclipse log viewing)
log4j.appender.C1=org.apache.log4j.ConsoleAppender
log4j.appender.C1.layout=org.apache.log4j.PatternLayout
log4j.appender.C1.layout.ConversionPattern=%d %p %c.%M - %m%n


# Loggers example
log4j.logger.edu.mit.apr.hires.service.SapHireService=DEBUG

# Root logger
log4j.rootLogger=INFO, C1, F1

Levels of logging:
 
TRACE (gives you more than DEBUG)
DEBUG (The DEBUG Level designates fine-grained informational events that are most useful to debug an application - more than INFO)
INFO (The INFO level designates informational messages that highlight the progress of the application at coarse-grained level - more than WARN)
WARN (The WARN level designates potentially harmful situations - more than ERROR)
ERROR (The ERROR level designates error events that might still allow the application to continue running)
FATAL (The FATAL level designates very severe error events that will presumably lead the application to abort)