Troubleshooting Guide

Logs and Debugging
September 2009 15
The available debugging thresholds are displayed in Table 5.
NOTE: Not all thresholds can be used in all configuration files. See
the procedures below for which thresholds can be used is particular
files.
To enable debugging in files with a *.cfg extension:
1. In a text editor, open the desired configuration file.
2. Under the section headed [Debug Log], set the debugging threshold to
DEBUG, CALL, TRACE, or DUMP. For example:
Threshold=DEBUG
The line might already exist or you might have to add a new line.
3. Save the configuration file.
The change takes effect immediately. You do not have to restart the
application or service.
To enable debugging in files with a *.properties extension:
1. In a text editor, open the desired configuration file.
2. Locate the line that starts with:
log4j.rootLogger=<threshold>#com.spanlink …
and replace <threshold> with DEBUG, TRACE, STACK, or DUMP.
3. Locate the line that starts with:
Table 5. Debugging Thresholds
Threshold Description
Debug Usually sufficient for diagnosing a problem. Will not affect system
performance.
Call Tracks function entry and exit.
Trace Provides a large amount of diagnostic information. May affect
system performance.
Stack Provides only stacktraces, which give more debugging information
when errors and warnings occur.
Dump Provides a very large amount of detailed diagnostic information.
Likely to affect system performance.
Off Turns off debugging.