Repository: qpid-jms
Updated Branches:
  refs/heads/master 729162d5b -> 612539463


QPIDJMS-47: minor tweak, formatting etc


Project: http://git-wip-us.apache.org/repos/asf/qpid-jms/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-jms/commit/61253946
Tree: http://git-wip-us.apache.org/repos/asf/qpid-jms/tree/61253946
Diff: http://git-wip-us.apache.org/repos/asf/qpid-jms/diff/61253946

Branch: refs/heads/master
Commit: 6125394632264ab0ad43b8601c001a38eb71309c
Parents: 729162d
Author: Robert Gemmell <[email protected]>
Authored: Mon May 11 14:34:05 2015 +0100
Committer: Robert Gemmell <[email protected]>
Committed: Mon May 11 14:34:05 2015 +0100

----------------------------------------------------------------------
 qpid-jms-docs/Configuration.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/qpid-jms/blob/61253946/qpid-jms-docs/Configuration.md
----------------------------------------------------------------------
diff --git a/qpid-jms-docs/Configuration.md b/qpid-jms-docs/Configuration.md
index 368b6c7..3c34ec2 100644
--- a/qpid-jms-docs/Configuration.md
+++ b/qpid-jms-docs/Configuration.md
@@ -163,10 +163,10 @@ These options apply to the behaviour of certain AMQP 
functionality.
 
 ## Logging
 
-The client makes use of the SLF4J API, allowing users to select a particular 
logging implementation based on their needs by supplying a SLF4J 'Binding', 
such as *slf4j-log4j*. More details on SLF4J are available from 
http://www.slf4j.org/.
+The client makes use of the SLF4J API, allowing users to select a particular 
logging implementation based on their needs by supplying a SLF4J 'binding', 
such as *slf4j-log4j* in order to use Log4J. More details on SLF4J are 
available from http://www.slf4j.org/.
 
 The client uses Logger names residing within the *org.apache.qpid.jms* 
heirarchy, which you can use to configure a logging implementation based on 
your needs.
 
 When debugging some issues, it may sometimes be useful to enable additional 
protocol trace logging from the Qpid Proton AMQP 1.0 library. There are two 
options to achieve this:
-+ Set the environment variable (not Java system property) *PN_TRACE_FRM* to 
true, which will cause Proton to emit frame logging to stdout.
-+ Add the option amqp.traceFrames=true to your connection URI to have the 
client add a protocol tracer to Proton, and configure the 
*org.apache.qpid.jms.provider.amqp.FRAMES* Logger to *TRACE* level to include 
the output in your logs.
++ Set the environment variable (not Java system property) *PN_TRACE_FRM* to 
*true*, which will cause Proton to emit frame logging to stdout.
++ Add the option *amqp.traceFrames=true* to your connection URI to have the 
client add a protocol tracer to Proton, and configure the 
*org.apache.qpid.jms.provider.amqp.FRAMES* Logger to *TRACE* level to include 
the output in your logs.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to