log4j log viewer

Tomcat under the use of log4j take over catalina.out log file generation, storage by day, solve catalina.out log file too big problem 1. Prepare jar Package: Log4j-1.2.17.jar (download from http://www.apache.org/dist/logging/log4j/1.2.17/) Tomcat-juli.jar, Tomcat-juli-adapte

log4j log File configuration ------------------------------------------------------------------------ first, the log device configuration # root Logger (other logs are inherited from this logger) # Default Level=debugLog4j.rootlogger=info, A1, A2 (a1,a2 for Appender) # Level of the log Log4j.logger.a=info,a1 Log4j.logg

1. Add log4j and slf4j jar packages2. Web. xml:[HTML]View Plaincopyprint? context-param> -- param-name>log4jconfiglocationparam-name> -- param-value>classpath:log4j.propertiesparam-value> context-param> context-param> --- param-name>log4jrefreshintervalparam-name> param-value>10000param-value> context-param> listener> listener-class>org.springframework.web.util.log4jconfiglistener Listener-class>

It has been a while since you used log4j for log output in spring, but sometimes you find that log files are already stored according to their ideals, but there are some baffling project log files that appear in Tomcat (because the project's log files are named after the pro

,stdout,d, E ### output to console ### Log4j.appender.stdout = Org.apache.log4j.Conso Leappender Log4j.appender.stdout.Target = System.out Log4j.appender.stdout.layout = org.apache.log4j.PatternLayout Log4j.appender.stdout.layout.ConversionPattern =%d{absolute}%5p%c{1}:%l-%m%n ### output to log file ### LOG4J.APPENDER.D = O Rg.apache.log4j.DailyRollingFileAppender Log4j.appender.d.file = d:/log4j/

Write Log two purposes: development phase of debugging, on-line phase tracking System bugs------General code consumption of 4% What is the difference between log technology and traditional System.out? The log is divided into levels to control whether information is exported to the log file

First of all, these two are log systems.Just slf4j is a simple façade log system simply to provide some column log interfaces without a specific implementation similar to JDBC but simpler than JDBC becauseIt does not need to load the driver to add only its specific package. And log4j himself alone can be a complete

Message that specifies information that can highlight the operation of an application at a coarse-grained level OFF This is the highest level, in order to turn off logging TRACE Specify less granular information events than debug WARN Specify a situation that is potentially harmful How does the log level work?Level p levels use Q when logging requests are logged, if P>=Q is e

Note: this information is searched through the network and then sorted into First of all, to explain the parameters of the configuration file, so that the configuration can be reasonable. Description of parameter meaning: Configure Root Logger Its syntax is: Log4j.rootlogger = [level], appenderName1, appenderName2, ... Level: Is the priority of the logging, divided into the levels you define by off, FATAL, ERROR, WARN, INFO, DEBUG, all, or a person. LOG4