Message log files contain the messages displayed on stdout,
runtime errors and application logging, if it exists. The following
log files are created in the $DTJ_LOGS directory,
which by default, is /var/dirTalk/DTBE/dtj_logs:
- log.n.log, created on each machine running
the Java and VoiceXML environment,
where n is a number between 1 and 10 (by default). This
file contains a binary representation of runtime errors and VoiceXML
application logging, if it exists.
- <nodename>.out, created by each node. This
file catches messages not caught by the log.n.log file.
It contains messages that are sent to stdout,
for example, Java application messages printed using System.out.println().
It is a standard text file that does not need to be formatted for
viewing.
The
log.n.log file is a cyclic file. Logging
will initially be output to
log.1.log. When this
file reaches a size of 5000 Kb (by default), logging will be output
to
log.2.log, and so on. When this process has continued
until
log.10.log is full, the first log file will
be overwritten and the cycle continues. You can change the
output directory, size, and number of the log files
by using the dtjit configuration
tool or by editing the following properties in
the
dtj.ini file:
- log.directory
- log.filesize
- log.numberoflogs
Note that the
log.filesize property is stored
in kilobytes, so to increase the value to 10000 Kb from the default
value of 5000, you would edit the entry to:
log.filesize=10000
Use the
dtjflog command to format the
log.n.log file
so that you can read it. For example, to format
log.2.log to
a file called
log2.out:
dtjflog -o log2.out log.2.log
This command is explained in full in dtjflog script.
Note: The nodename.out file
is backed up to nodename.out.bak when
the node starts. This applies to application nodes and voice response
nodes when started. If nodename.out already
exists, it is renamed to nodename.out.bak before
the new file is created.