An effective first step when troubleshooting is to enable verbose logging. You can do this by setting the following java system property:
-Dparasoft.logging.config.file=<PATH_TO_LOG4J_CONF_FILE>
In this property, PATH_TO_LOG4J_CONF_FILE must point to a valid log4j configuration file. There is a default configuration file (debug.logging.xml) located at <TOMCAT_INSTALLATION>/webapps/em/config/.
How you set the java system property depends on your installation environment, but in a common Apache Tomcat installation you can set the property by using a shell or bat script called setenv and putting that in the tomcat bin directory. Below are sample commands that can be added to either type of script.
export JAVA_OPTS="$JAVA_OPTS -Dparasoft.logging.config.file=$CATALINA_BASE/webapps/em/config/debug.logging.xml"
set "JAVA_OPTS=%JAVA_OPTS% -Dparasoft.logging.config.file=%CATALINA_BASE%/webapps/em/config/debug.logging.xml"
The default java logging for Tomcat is pretty verbose and, in most cases, should provide more than enough information for your troubleshooting needs, but you can adjust the verboseness by modifying the logging levels in the logging.properties file located at <TOMCAT_INSTALLATION>/conf/.
