Tomcat Standalone Troubleshooting

Procedure

1. Make sure the server is shutdown. Do this by typing "shutdown.sh"
2. Try restarting the server. Do this by typing "startup.sh"
3. Read the output from the computer
4. If the output is "startup.sh: command not found" - This means that the computer does not know where to find the Tomcat startup program. We need to verify that the Tomcat bin directory is in the path.
5. If the output ends with "<install-dir>/jakarta-tomcat/bin/startup.sh: Permission Denied"  - This means that the computer has found the startup.sh program but has insufficient privileges to actually run the program. We need to verify that the startup.sh has execute  and read permission.
6. If the last line of the output is "Cannot find JAVA. Please set your PATH" - This means that the computer has found the Tomcat startup program, but it cannot find the Java interpreter. We need to verify that the Java bin directory is in the path.

1. Check to see if you have a "jakarta-tomcat/bin" directory in your path - Do this by typing "env | grep jakarta-tomcat/bin"
2. If the output line begins with "PATH=" - This means that a "jakarta-tomcat/bin" directory is indeed in the path. We need to verify that the directory contains a startup.sh file.
3. If there is no output - This means that there is no "jakarta-tomcat/bin" directory in the path. We need to double check the .bash_profile file for the bash shell or the .cshrc file for the tcsh.
4. If there is output but there is no line that begins with "PATH=" - The directory "jakarta-tomcat/bin" is set in some other environment variable. We need to double check the .bash_profile file for the bash shell or the .cshrc file for the tcsh.

Verify that the startup.sh has execute and read permission.

1. Determine where the environment believes the "jakarta-tomcat/bin"