Debug using log4j
Debugging
with log4j configurations
Unfortunately setting of logging in the Java Broker is not simply
a matter of setting one of WARN,INFO,DEBUG. At some point in the
future we may have more BAU logging that falls in to that
category but more likely is that we will have a varioius config
files that can be swapped in (dynamically) to understand what is
going on.
This page will be host to a variety of useful configuration
setups that will allow a user or developer to extract only the
information they are interested in logging. Each section will be
targeted at logging in a particular area and will include a full
log4j file that can be used. In addition the logging
category elements will be presented and discussed so
that the user can create their own file.
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
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.
]]>
Debugging My
Application
This is the most often asked for set of configuration. The goals
of this configuration are to record:
New Connections
New Consumers
Message Publications
Message Consumption
Identify slow consumers
Closing of Consumers
Closing of Connections
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
]]>