The default logging configuration:
uses a log severity of INFO.
has a log file per engine named
<engine-name>.log
(see the section called “Deploy tool logging” for special log file
handling for the deploy tool).
if user configuration has not defined a duplicate message filter, a duplicate message filter that suppresses messages after the ninth repetition is installed; the tenth and subsequent messages are suppressed. The log message generated for the suppressed messages uses the same category and severity as the suppressed message.
unless specifically set by user configuration, defines 3rd-party library logger configuration that adjusts log levels to decrease chattiness.
unless user configuration has explicitly set a root file
appender to the default value of the
com.tibco.ep.dtm.logging.logDirectory substitution
variable, log file rollover is set to a maximum file size of 10MB for
ten files.
The default log message format is:
"%d{yyyy-MM-dd HH:mm:ss.}%usecs%d{Z} [%process:%thread] %-5level %logger: %msg%n"When a fragment is deployed to an engine using the deploy tool, as opposed to part of an application archive, multiple log files are created per engine. The suffix indicates where the contents of the log file came from:
.log - runtime logging.
.out - fragment logging sent to standard
output.
.err - fragment logging sent to standard
error.
An audit log is configured for every node. It cannot be disabled. The audit log is configured:
with a log severity of INFO.
to use a file name of audit.log created in
the logs directory. The location and log file
name cannot be changed.
to disable additivity; audit log messages only get logged in the audit log.
The default audit log message format is:
"%d{yyyy-MM-dd HH:mm:ss.SSSZ}: %msg%n"A deadlock log is configured for every node. It cannot be disabled. The deadlock log is configured:
with a log severity of WARN.
to use a file name of deadlock.log created
in the logs directory. The location and log file
name cannot be changed.
to disable additivity; deadlock log messages only get logged in the deadlock log.
Please see the Analyzing Deadlocks section in the Performance Tuning Guide for details on the deadlock log message format.