| <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">11.2. Enabling Debug</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="JMS-Client-0-8-Logging.html">Prev</a> </td><th align="center" width="60%">Chapter 11. Logging</th><td align="right" width="20%"> <a accesskey="n" href="JMS-Client-0-8-Appendix-Exceptions.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="JMS-Client-0-8-Logging-EnablingDebugLogging"></a>11.2. Enabling Debug</h2></div></div></div><p>If you are experiencing a problem, it can be informative to enable debug logging to allow | |
| the behaviour of the Client to be understood at a deeper level.</p><p>To do this, set the <code class="literal">org.apache.qpid</code> logger to | |
| <code class="literal">DEBUG</code>.</p><p>If you are using Apache Log4j with a log4j.properties file, this simply means adding (or | |
| changing) the following line:</p><pre class="screen"> | |
| log4j.logger.org.apache.qpid=DEBUG | |
| </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 class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="JMS-Client-0-8-Logging.html">Prev</a> </td><td align="center" width="20%"><a accesskey="u" href="JMS-Client-0-8-Logging.html">Up</a></td><td align="right" width="40%"> <a accesskey="n" href="JMS-Client-0-8-Appendix-Exceptions.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter 11. Logging </td><td align="center" width="20%"><a accesskey="h" href="JMS-Client-Book.html">Home</a></td><td align="right" valign="top" width="40%"> Appendix A. Exceptions</td></tr></table></div></div> |