Wiki source code of Logging
Version 3.3 by Vincent Massol on 2009/06/20
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
3.1 | 1 | #startfloatingbox() |
| 2 | *Contents* | ||
| 3 | #toc ("2" "3" "") | ||
| 4 | #endfloatingbox() | ||
| 5 | |||
| |
1.1 | 6 | 1 Logging |
| 7 | |||
| |
1.3 | 8 | XWiki uses Commons Logging for logging. By default XWiki is configured so that Commons Logging uses log4J. XWiki's Log4J configuration is located inside XWiki's JAR (xwiki.jar), in a <tt>[log4j.properties>http://fisheye2.cenqua.com/browse/~raw,r=trunk/xwiki/xwiki-platform/core/trunk/src/main/resources/log4j.properties]</tt> file. XWiki' JAR is itself located in your <tt>WEB-INF/lib/</tt> directory. |
| |
1.1 | 9 | |
 |
3.2 | 10 | #info("By default XWiki is configured to log everything both on the console and in a xwiki.log file located in the directory from where you have started the JVL. This is usually the directory from where you have started your application server/Servlet container. It's recommended to either start the JVM from a location where it's ok to output the xwiki.log file or to create a custom Log4J configuration as explained below.") |
| |
1.4 | 11 | |
| |
1.1 | 12 | 1.1 Using a custom Log4J configuration |
| 13 | |||
| 14 | The best solution is to create a new <tt>log4j.properties</tt> file in your <tt>WEB-INF/classes</tt> directory. It'll thus override the one from the XWiki JAR. As an example, here's a sample configuration: | ||
| 15 | |||
| |
1.2 | 16 | {code:none} |
| |
1.6 | 17 | ### Direct log messages to stdout |
| |
1.1 | 18 | log4j.appender.stdout=org.apache.log4j.ConsoleAppender |
| 19 | log4j.appender.stdout.Target=System.out | ||
| 20 | log4j.appender.stdout.layout=org.apache.log4j.PatternLayout | ||
| |
3.3 | 21 | log4j.appender.stdout.layout.ConversionPattern=%d [%X{url}] [%t] %-5p %-30.30c{2} %x - %m %n |
| |
1.1 | 22 | |
| 23 | log4j.appender.file=org.apache.log4j.RollingFileAppender | ||
| 24 | log4j.appender.file.File=xwiki.log | ||
| 25 | log4j.appender.file.MaxFileSize=10MB | ||
| 26 | log4j.appender.file.MaxBackupIndex=50 | ||
| |
2.1 | 27 | log4j.appender.file.layout=org.apache.log4j.PatternLayout |
| |
3.3 | 28 | log4j.appender.file.layout.ConversionPattern=%d [%X{url}] [%t] %-5p %-30.30c{2} %x - %m %n |
| |
1.1 | 29 | |
| |
1.6 | 30 | ### By default everything that is of warning or severity WARN, ERROR or FATAL is logged both to |
| 31 | ### the console and to the xwiki.log file. | ||
| |
1.1 | 32 | log4j.rootLogger=warn, stdout, file |
| 33 | |||
| |
1.6 | 34 | ### Hibernate logging options |
| |
1.1 | 35 | log4j.logger.org.hibernate=warn |
| 36 | log4j.logger.org.hibernate.SQL=warn | ||
| 37 | log4j.logger.org.hibernate.type=warn | ||
| 38 | log4j.logger.org.hibernate.ps.PreparedStatementCache=warn | ||
| 39 | |||
| |
1.6 | 40 | ### XWiki logging configuration |
| |
3.3 | 41 | log4j.logger.org.xwiki=info |
| |
1.1 | 42 | log4j.logger.com.xpn.xwiki=warn |
| 43 | log4j.logger.com.xpn.xwiki.render.XWikiRadeoxRenderEngine=warn | ||
| |
2.1 | 44 | log4j.logger.com.xpn.xwiki.store.migration=info |
| |
1.1 | 45 | |
| |
2.1 | 46 | ### Deactive Struts warnings |
| |
1.1 | 47 | log4j.logger.org.apache.struts.util.RequestUtils=error |
| 48 | |||
| |
1.6 | 49 | ### Deactivate JGroups warnings |
| |
1.1 | 50 | log4j.logger.org.jgroups=error |
| |
2.1 | 51 | |
| 52 | ## Deactive PDF Export CSS Applier warnings | ||
| 53 | log4j.logger.info.informatica.doc.style.css.dom=error | ||
| 54 | log4j.logger.org.apache.fop.layoutmgr.inline.ContentLayoutManager=error | ||
| |
1.1 | 55 | {code} |
| 56 | |||
| 57 | Refer to Log4J's documentation to understand the settings. As an example, to turn on Hibernate's calls, just set the following: | ||
| 58 | |||
| 59 | {code} | ||
| 60 | log4j.logger.org.hibernate.SQL=debug | ||
| 61 | {code} | ||
| 62 | |||
| |
3.1 | 63 | 1.1 Activating the XWiki monitoring feature |
| 64 | |||
| 65 | #info("The monitoring feature is already active in the default configuration.") | ||
| 66 | |||
| 67 | XWiki has a feature to monitor times spent in its major components. To activate it, you need to: | ||
| 68 | * Enable the Monitor plugin by adding/modifying the following plugin definition in the <tt>xwiki.cfg</tt> configuration file: | ||
| 69 | |||
| 70 | {code:none} | ||
| 71 | xwiki.plugins=\ | ||
| 72 | [...] | ||
| 73 | com.xpn.xwiki.monitor.api.MonitorPlugin | ||
| 74 | {code} | ||
| 75 | |||
| 76 | * Enable it by adding/modifying the following in the <tt>xwiki.cfg</tt> configuration file: | ||
| 77 | |||
| 78 | {code:none} | ||
| 79 | xwiki.monitor=1 | ||
| 80 | {code} | ||
| 81 | |||
| 82 | * Since the plugin logs everything under the <tt>DEBUG</tt> severity you also need to configure Log4J (as described above) by adding the following in <tt>log4j.properties</tt>: | ||
| 83 | |||
| 84 | {code:none} | ||
| 85 | log4j.logger.com.xpn.xwiki.monitor=debug | ||
| 86 | {code} | ||
| 87 |
