Temporarily Setting Debug Thresholds
By default, the server configuration uses a java system property (logj4.default.log.level) to set the logging threshold for several categories to the WARN threshold. When you start the server with the -d startup option, the logj4.default.log.level variable is set to DEBUG. As a result, the server collects messages for the categories at the DEBUG threshold until the server is shut down. Use this the -d startup option to run the server in debug mode. This is an easy way to temporarily increase the log level for many categories to perform troubleshooting.
The following section of the logging configuration shows the categories that are affected by the -d startup option:
# default level controled by -d=DEBUG otherwise =WARN
log4j.category.Framework=${log4j.default.log.level}
log4j.category.frameworkInit=${log4j.default.log.level}
log4j.category.dataAccess=${log4j.default.log.level}
log4j.category.jsp=${log4j.default.log.level}
log4j.category.jsf=${log4j.default.log.level}
log4j.category.directory=${log4j.default.log.level}
log4j.category.portlet=${log4j.default.log.level}
log4j.category.classManager=${log4j.default.log.level}
log4j.category.taglibs=${log4j.default.log.level}
log4j.category.mail=${log4j.default.log.level}
log4j.category.search=${log4j.default.log.level}
log4j.category.messaging=${log4j.default.log.level}
log4j.category.notifications=${log4j.default.log.level}
log4j.category.schedule=${log4j.default.log.level}
log4j.category.version=${log4j.default.log.level}
log4j.category.task=${log4j.default.log.level}
log4j.category.webservice=${log4j.default.log.level}
log4j.category.wsclient=${log4j.default.log.level}
For instructions for how to start the server using the -d startup option, see
Basic Command Line Syntax for
My webMethods Server.