I was stuck by this bug for a day today and must be written down.
Yesterday, I used the command jar to package a very simple small project into a war package. It was successfully deployed under the tomcat manager page, but the page display was problematic. Then I thought that I repackaged it today. I didn’t expect to repackage it and deploy it to run and report 404. The war package in the webapps of tomcat can’t be automatically decompressed, but after manual decompression, the page still appears as yesterday, but the display is still there. problem. So, I was stuck here for a day, looking for errors, checking the configuration, and doing it again on the fellow Cao Ge server. It was still unsuccessful, and I accidentally uninstalled the files that were originally deployed. . .
Finally, just now, with the mentality of giving it a try, I used a particularly simple method of packaging war packages on the Internet, which is to compress it into a zip first, then change the suffix name to war, and then redeploy it. I didn't expect it! ! ! Succeeded! ! ! Even my page effect is completely out! Crying, I've been stuck with this kind of problem for a day, and I trouble my colleagues to check it out, but it's okay to solve it, just record it here!
Let's show you the page that runs successfully, because it is a test, I took a particularly simple page:
