Tomcat problems
From Swivel Knowledgebase Wiki
Contents |
Overview
Tomcat Problems
Prerequisites
Apache Tomcat
Symptoms
Tomcat will not start or stops
solutions
Check the PINsafe and Tomcat logs
Check appliance disk space, a lack of disk space may stop Tomcat from starting
Is there a PINsafe filter stopping access from certain IP addresses, see Filter IP How to Guide
A process to monitor Tomcat on appliances is detailed here MON Service Monitor How to guide
Check that the Java path is correct and that the Java nd Tomcat are both 32 bit or 64 bit
Tomcat will not start
Check to see that there are no other applications that are using port 8080 or have installed an Apache Tomcat Webserver. Use netstat -b to see which ports are being used.
Tomcat Stoppping
See Tomcat stops after logout out of CMI
Ensure that the Tomcat Webapps folder does not have multiple instances of PINsafe that have been copied from the installed pinsafe folder. Multiple instances of PINsafe can be used, but need to be created from a .war file rather than copying the existing install to a new folder.
If a Stack trace is produced, try logging back into the status page http:(s)//<PINsafe_IP>:8080/pinsafe. If this is not available then check the Tomcat logs for any errors. See specific problems relating to Tomcat at Tomcat problems. See Also Transport Attribute nil attribute but is not nillable.
If an external database is being used such as MySQL on an appliance, and the database is not available, such as MySQL is not running then it can produce a stack trace error during PINsafe Administration login.
Tomcat Starts but PINsafe not available
PINsafe 3.8 onwards may display a pinsafe/error page, earlier versions may show that the login page is not available. This can be caused by:
- Corrupt config.xml - check the file size of the config.xml file
- Database is not running. For appliances check that MySQL is running where used.
