As I understand it, Slide has its own Logger implementation which uses
one of several backends to do the actual logging: log4j, jdk14, or a
simple logger. The logging-level in Domain.xml controls the verbosity of
the internal Logger, before is sent to the backend. Thus, if you want to
control verbosity in log4j.properties, for example, you set
logging-level to the highest so log4j receives all logging events and
then use log4j configuration to filter what you want. I don't think
there's any significant difference in performance if logging-level is
set to the highest because a test always has to be done anyway to decide
whether to send to the backend and communicating with the backend
involves no I/O. Setting a high verbosity level on the backend will
affect performance, of course, because of the higher output to the
console or file.
Carlos
Warwick Burrows wrote:
I don't understand the relationship between this setting and those in the
log4j.properties. So do you have any idea whether setting the logger-level
in the Domain.xml causes a performance hit? Ie. by enabling "level 7"
logging paths in the Slide server that would normally be skipped over?
I'm wondering whether I should leave this setting at level 7 on a running
system, or whether it will slow the server down. Or if I set the
logging-level lower eg. "1" will I still be able to get more verbose levels
of trace out of the server by changing log4j.properties?
Thanks,
Warwick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
