为何部署时.war文件未在云服务器webapps目录自动解压？

Hey there, let's work through why your Spring-MVC WAR file isn't auto-unpacking on Google Cloud and get your app accessible in no time! Here are the most common fixes to try:

1. Verify Your Application Server's Auto-Unpack Settings #

If you're using Tomcat (the go-to server for Spring-MVC apps), double-check that auto-deployment and unpacking are enabled:

• SSH into your Google Cloud instance and head to your Tomcat's conf directory (usually /opt/tomcat/conf/).
• Open the server.xml file and locate the <Host> element. Make sure it has these attributes set to true:

  <Host name="localhost"  appBase="webapps"
        unpackWARs="true" autoDeploy="true">
  

• Save the file and restart Tomcat with this command:

  sudo systemctl restart tomcat
  

For Google App Engine Standard Environment, ensure your app.yaml specifies the correct runtime (e.g., runtime: java17) and that your WAR is placed in the root of your deployment directory.

2. Confirm You Uploaded the WAR to the Correct Directory #

Tomcat only auto-unpacks WAR files placed in its webapps folder. Double-check in FileZilla that you dragged your WAR into:
/opt/tomcat/webapps/ (or the equivalent path for your server setup). If you uploaded it to a different folder, move it to webapps and restart the server.

3. Check File Permissions #

Uploaded files sometimes have restrictive permissions that block the server from accessing them:

• SSH into your instance and run this to check permissions on your WAR file:

  ls -l /opt/tomcat/webapps/your-war-file.war
  

• You should see permissions like -rw-r--r-- (read/write for owner, read for others). If not, fix them with:

  sudo chmod 644 /opt/tomcat/webapps/your-war-file.war
  

• Restart Tomcat afterward to apply the changes.

4. Inspect Server Logs for Errors #

Logs are your best debugging tool. Check Tomcat's catalina logs to find out why unpacking failed:

• Run this command to view real-time logs:

  tail -f /opt/tomcat/logs/catalina.out
  

• Look for messages like "failed to unpack WAR", "missing dependencies", or file corruption. These will point you to the exact issue (e.g., a corrupted WAR or missing library).

5. Try Manual Unpacking #

If auto-unpacking still won't work, manually unpack the WAR to test if the app itself functions:

• Navigate to the webapps directory:

  cd /opt/tomcat/webapps/
  

• Unpack the WAR into a directory named after your app (this is what auto-unpacking would do):

  unzip your-war-file.war -d nameOfProgramme
  

• Restart Tomcat and try accessing 143.9.xxx.xxx:8080/nameOfProgramme again. If this works, the problem is definitely with the auto-unpack configuration.

6. Validate Your WAR File Locally #

Before blaming the server, make sure your WAR is valid:

• Unpack the WAR on your local machine and check if all critical files are present (like WEB-INF/web.xml and your compiled classes).
• Deploy the WAR to a local Tomcat instance. If it doesn't run locally, fix your packaging in IntelliJ:
  • Double-check your artifact configuration to ensure all dependencies (Spring libraries, etc.) are included in the WAR.
  • Re-build the WAR file and re-upload it to Google Cloud.

内容的提问来源于stack exchange，提问作者Agnes Palit