Owners Manual

Troubleshooting Your Application | Troubleshooting
OMNM 6.5.2 User Guide 711
Debug
When an error appears in logs (see Logs on page 713) it indicates for which Java class you need to
increase the level of logging if you want debugging information. You can change logging levels to
get additional (debug) information.
NOTE:
Best practice is to now alter Log Categories in the Application Server Statistics portlet by clicking that
button. This alteration simplifies editing
log4j.xml files since it provides a graphical interface, and if
you have more than one server, it alters the log levels for all servers at once.
Flipdebug
You can easily turn debug on or off with the flipdebug script. Run this while the application
server is running and remember to wait a few moments for the application server to pick up your
changes. Here is the usage (just type the script name to see these options):
Usage: flipdebug [-d] [-t] [-r] [-h|-?] [-p] product[,product]
-d Turn on debug for all packages
-t Turn on trace for all packages
-p Turn on trace/debug only for product[,product] (no spaces between
products)
-r Revert to original log4j settings
-h|-? Display usage
The product name in -p matches the directory under owareapps . The debug and trace write to
the log and to stdout.
Fine-Tuning Debug
To fine tune debug further, create a file, whose name ends in log4j.xml in the
owareapps\installprops\server\conf directory with the categories you want changed. If
the class does not exist within the
log4j file, add it and set it to debug. Changes preserved in such
a file remain in place until you change them again, and are not overwritten when software upgrades
occur.
To increase logging levels to DEBUG, change
WARN or INFO to DEBUG in categories like the
following:
- <category name="com.dorado.redcell">
- <priority value="WARN"/>
- </category>
...
- <category name="redcell">
- <priority value="WARN"/>
- </category>
- <category name="RedCell">
- <priority value="INFO"/>
- </category>