You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by ra...@apache.org on 2010/06/09 18:04:34 UTC

svn commit: r953064 - /qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml

Author: rajith
Date: Wed Jun  9 16:04:34 2010
New Revision: 953064

URL: http://svn.apache.org/viewvc?rev=953064&view=rev
Log:
Added a recommended log level to the java loggin section.

Modified:
    qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml

Modified: qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml
URL: http://svn.apache.org/viewvc/qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml?rev=953064&r1=953063&r2=953064&view=diff
==============================================================================
--- qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml (original)
+++ qpid/trunk/qpid/doc/book/src/Programming-In-Apache-Qpid.xml Wed Jun  9 16:04:34 2010
@@ -2951,7 +2951,7 @@ producer.send(m);
 
       <para>For more information on how to configure log4j, please consult the log4j documentation.</para>
 
-      <para>If using the log4j binding please ensure to set the log level explicitly. Otherwise log4j will default to DEBUG level which will degrade performance.</para>
+      <para>If using the log4j binding please ensure to set the log level for org.apache.qpid explicitly. Otherwise log4j will default to DEBUG which will degrade performance considerably due to excessive logging. Recommended logging level for production is WARN.</para>
 
       <example>
       <para>You could place the snippet below in a log4j.properties file and place it in the classpath or explicitly specify it using the -Dlog4j.configuration property. The following configures the qpid client to log at the WARN level</para>



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org