I had a Java application deployed (setup by someone else) and I’ve been going through the process of improving it myself (read. breaking it). I need some help please
I appear to have HTTPS working ok and have now got Tomcat working, except it only shows a blank page when you go to the URL. When you inspect the page it shows a raft of 404 errors where it doesn’t seem to be able to find the .jps files. This makes me think a path is incorrectly set somewhere or a permissions issue?
TBH the whole file structure in this directory is confusing to me, there seems to be multiple versions of the same files all over the place.
File structure:
Root. 1. bin
- DATA
- Projects
- Tomcat
- admin (admin console - used to be accessed using URL/site-admin 1.apache-tomcat-8.5.29
- bin
- conf
- lib
- logs
- webapps 1. ROOT
- SITE
- SITE-WEB*
- SITE-Admin*
- back-end (this has the .WAR file in it)
- frount-end (presume spelling mistake) - (this seems to mimic the content of both the webapps/site-web directory and webapps/ROOT) 2. etc = apache2
- var
- usr
The tomcat log seems to be clear and running ok.
Help would be greatly appreciated and can post additional info if required.
thanks
Colonel Yeehaw
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hello,
without more information on such issues, I would assume the problem lies in the configuration files. Having said that here are some tips what to troubleshoot when in such situations
- Check if the application is deployed properly: Ensure that your application is deployed correctly under the
webappsfolder in Tomcat. Typically, the application should be in the form of a.warfile or an extracted folder. In your case, the application should be insidewebapps/SITEorwebapps/ROOT. - Ensure that the context path is set correctly: If your application is not under the
ROOTfolder, you need to access it using the context path (e.g.,https://yourdomain.com/SITE). If your application is under theROOTfolder, it should be accessible directly from the base URL (e.g.,https://yourdomain.com/) - Check the Tomcat logs: Inspect the Tomcat logs in the
logsfolder (e.g.,catalina.out,localhost.*.log) for any errors or warnings related to your application. These logs can provide useful information about issues with the deployment, configuration, or the application itself. - Check the application logs: Your application might also have its own log files. Look for any application-specific log files in the
webapps/SITE/WEB-INF/logsfolder or any other folder where your application stores logs. These logs can provide more information about issues within the application. - Check file permissions: Ensure that the Tomcat user has read and execute permissions on your application files and folders. You can update the permissions using the following command (replace
/path/to/tomcat/webappswith the actual path to yourwebappsfolder):
- sudo chown -R tomcat:tomcat /path/to/tomcat/webapps
- sudo chmod -R 755 /path/to/tomcat/webapps
- Check the server.xml configuration: Verify that the
server.xmlfile in theconffolder is correctly configured. Ensure that there is a<Host>element with the correctappBasepointing to thewebappsfolder. For example:
- <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.