| <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter 11. Logging</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="JMS-Client-0-8-System-Properties.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="JMS-Client-0-8-Logging-EnablingDebugLogging.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="JMS-Client-0-8-Logging"></a>Chapter 11. Logging</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="section"><a href="JMS-Client-0-8-Logging.html#JMS-Client-0-8-Logging-RecommendedProductionLoggingLevel">11.1. Recommended Production Logging Level</a></span></dt><dt><span class="section"><a href="JMS-Client-0-8-Logging-EnablingDebugLogging.html">11.2. Enabling Debug</a></span></dt></dl></div><p>The Client uses the <a class="link" href="http://www.slf4j.org" target="_top">Apache SLF4J</a> logging | |
| framework. All logging activity created by the client is directed through the SLF4J API. SLF4J | |
| is a is a façade for other common logging frameworks. This makes it easy for application authors | |
| to use their prefered logging framework in their application stack, and have the Client | |
| use it too. </p><p>SLF4J suppplies bindings for many common logging frameworks (<a class="link" href="http://docs.oracle.com/javase/7/docs/api/java/util/logging/package-summary.html" target="_top">JUL</a>, <a class="link" href="http://logging.apache.org/log4j/1.2/" target="_top">Apache Log4J</a>, <a class="link" href="http://logback.qos.ch" target="_top">Logback</a>.</p><p>Include the SLF4J binding corresponding to the logging framework of your choosen logging | |
| framework on classpath. For full details, see the SLF4J <a class="link" href="http://www.slf4j.org" target="_top">documentation</a>.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="JMS-Client-0-8-Logging-RecommendedProductionLoggingLevel"></a>11.1. Recommended Production Logging Level</h2></div></div></div><p>In production, it is recommended that you configure your logging framework is configured | |
| with logger <code class="literal">org.apache.qpid</code> set to <code class="literal">WARN</code>.</p><p>If you are using Apache Log4j with a log4j.properties file, this simply means adding the | |
| following line:</p><pre class="screen"> | |
| org.apache.qpid=WARN | |
| </pre><p>If you are using another logging framework, or you are using Log4j but configuring in | |
| another manner, refer to the documentation accompanying the logging framework for details of | |
| how to proceed.</p></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-System-Properties.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="JMS-Client-0-8-Logging-EnablingDebugLogging.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter 10. System Properties </td><td align="center" width="20%"><a accesskey="h" href="JMS-Client-Book.html">Home</a></td><td align="right" valign="top" width="40%"> 11.2. Enabling Debug</td></tr></table></div></div> |