Show Table of Contents
21.3. QPID AMQP 1.0 JMS Client 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 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 hierarchy, 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_FRMtotrue, which will cause Proton to emit frame logging to stdout. - Add the option
amqp.traceFrames=trueto your connection URI to have the client add a protocol tracer to Proton, and configure theorg.apache.qpid.jms.provider.amqp.FRAMESLogger toTRACElevel to include the output in your logs.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.