The Logging Interceptor is a pretty trivial Interceptor which just logs to Jakarta Commons Logging or log4j as messages are sent or acknowledged on a broker.
The default logging level used is INFO. If you want to increase/reduce the logging you can use change it via commons logging or log4j.
As of version 5.3 the logging Interceptor is more configurable. The idea is to log all events but be able to turn off logging for certain event groups by configuration.
Currently the following groups are supported:
|logAll||Log all Events||false|
|logMessageEvents || Events related with producing, consuming and dispatching messages||false|
|logConnectionEvents || Events related to connections and sessions||true|
|logTransactionEvents || Events related to transaction handling||false|
|logConsumerEvents || Events related to consuming messages||false|
|logProducerEvents || Events related to producing messages||false|
|logInternalEvents || Events normally not of Interest for users like failover, querying internal objects etc||false|
Only connection events logging is enabled by default.
You can enable the logging interceptor using the following XML configuration. This example enables all logging and disables the connection event logging: