From da5d14eb7aee6541779fcff82abbd9c53a003d80 Mon Sep 17 00:00:00 2001 From: Rajith Muditha Attapattu Date: Wed, 9 Jun 2010 15:52:07 +0000 Subject: Added a closing tag which was missing. Added a few tips in the java logging section. git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@953050 13f79535-47bb-0310-9956-ffa450edef68 --- qpid/doc/book/src/Programming-In-Apache-Qpid.xml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'qpid/doc/book/src/Programming-In-Apache-Qpid.xml') diff --git a/qpid/doc/book/src/Programming-In-Apache-Qpid.xml b/qpid/doc/book/src/Programming-In-Apache-Qpid.xml index 0995cc63c4..2c8db34866 100644 --- a/qpid/doc/book/src/Programming-In-Apache-Qpid.xml +++ b/qpid/doc/book/src/Programming-In-Apache-Qpid.xml @@ -2947,8 +2947,13 @@ producer.send(m); JMS Client Loggin The JMS Client logging is handled using SLF4J. A user can place a slf4j binding of their choice in the classpath and configure the respective logging mechanism to suit their needs. Ex bindings include log4j, jdk1.4 logging ..etc - Following is an example on how to configure Qpid logging with the log4j binding. + Following is an example on how to configure the client logging with the log4j binding. + For more information on how to configure log4j, please consult the log4j documentation. + + If using the log4j binding please ensure to set the log level explicitly. Otherwise log4j will default to DEBUG level which will degrade performance. + + 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 + + -- cgit v1.2.1