Page History

Debugging with log4j configurations

...

Currently the configuration that is available has not been fully documented and as such there are gaps in what is desired and what is available. Some times this is due to the desire to reduce the overhead in message processing, but sometimes it is simply an oversight. Hopefully in future releases the latter will be addressed but care needs to be taken when adding logging to the 'Message Flow' path as this will have performance implications.

Logging Connection State *Deprecated*

deprecation notice Version 0.6 of the Java broker includes Operational Status Logging functionality which improves upon these messages and as such enabling status logging would be more beneficial.
The configuration file has been left here for assistence with broker versions prior to 0.6.

The goals of this configuration are to record:

• New Connections
• New Consumers
• Identify slow consumers
• Closing of Consumers
• Closing of Connections

An additional goal of this configuration is to minimise any impact to the 'message flow' path. So it should not adversely affect production systems.

application-connections.xml

Debugging My Application

This is the most often asked for set of configuration. The goals of this configuration are to record:

...

NOTE: This configuration enables message logging on the 'message flow' path so should only be used were message volume is low.
Every message that is sent to the broker will generate at least four logging statements
application-debug.xml

Logging Connections

Logging Consumers

...