log4j conversionpattern example

Spring uses log4j, and there are 2 ways to do it.1. Do not make any configuration in Web. Xml.Log4j.properties placed in the Classpath root directory,The resulting log file does not have a relative path, and if a relative path is written, it is generated under the root path of the installation tomcat.2. Set in Web. Xml.Printing parameters: log4j Format the log information in a print format similar to the pr

Log4j-1.2.16.ja environment: myeclipse10 + log4j1.2.16 + jdk1.6 1. Create a Java project named log4jtest. 2. SetLog4j-1.2.16.jar copy to project root directory, right-click Project, properties, Java build path, add jars, selectLog4j-1.2.16.jar 3. InSource codeDirectory to create an XML file: log4j. xml. The configuration starts. The content is as follows: XML version = "1.0" encoding = "UTF-8"

Example of how MyBatis3 outputs SQL using log4j on the console, mybatis3log4j Why do I need to output SQL statements on the console? Of course, it is convenient for development and debugging. If a database-related operation encounters a problem, we can quickly troubleshoot the problem based on the output SQL statement. Output Information: [Org. mybatis. spring. SqlSessionUtils]-Creating a new SqlSession[O

With log4j, you can easily process logs in your project-control the destination of the Log information output (console, file, GUI component, or NT Event recorder), control the output format of each log (htmllayout layout format, patternlayout layout format, Simplelayout layout format or ttcclayout), controls the level of output log information (debug level, info level, warn level, error level, or fatal level), and so on. Here's a simple

steps: Create a new Java project and import the log4j jar package; Create the Log4j.properties profile and set it in the SRC directory;1 # Set the global output level2Log4j.rootlogger=Error,stdout,file3 4 # Output logs above the error level to the console5log4j.appender.stdout=Org.apache.log4j.ConsoleAppender6log4j.appender.stdout.target=System.out7log4j.appender.stdout.layout=Org.apache.log4j.PatternLayout8Log4j.appender.stdout.layout.conversio

preceding outputs and shields all the subsequent outputs. Here, we recommend two types: Error: only error information is recorded; debug: detailed information of all errors is recorded. In the production configuration, disable the "apply to console" option and only enable file). The following two consoles and files represent the location of log output, and the following two can be named at will, to be clear and easy to understand, you can use words with a glance. For

I have not written examples in the log4j usage notes. In this article, I will write a complete application instance of log4j. In the log4j usage notes, we already know that the same log information can be output to multiple output destinations at the same time. In the following example, I will demonstrate how to output

Here is an example of file pointing to a specific file instead of a folder. ### Set output encoding ###Log4j. appender. logfile. Encoding = UTF-8### Set log levels ###Log4j. rootlogger = debug, stdout, d, e ### Out print at console ###Log4j. appender. stdout = org. Apache. log4j