Spring Boot WAR包部署Tomcat服务器失败排查求助

Hey there, let’s walk through how to troubleshoot your Spring Boot WAR deployment issue on Linux Tomcat—since it works locally in Eclipse, we can narrow down the problem step by step. Here are targeted checks to identify and fix the root cause:

First, make sure your pom.xml is properly set up for external Tomcat deployment:

• Ensure the packaging type is set to war:

  <packaging>war</packaging>
  

• Exclude Spring Boot's embedded Tomcat (since we're using the external Tomcat server):

  <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-tomcat</artifactId>
      <scope>provided</scope>
  </dependency>
  

• Confirm your main application class extends SpringBootServletInitializer and overrides the configure method—this is required for deploying Spring Boot as a WAR to external containers:

  @SpringBootApplication
  public class YourApp extends SpringBootServletInitializer {
      @Override
      protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
          return application.sources(YourApp.class);
      }
  
      public static void main(String[] args) {
          SpringApplication.run(YourApp.class, args);
      }
  }
  

Spring Boot has strict compatibility with Tomcat versions:

• For Spring Boot 2.x: Use Tomcat 8.5.x or 9.0.x
• For Spring Boot 3.x: Use Tomcat 9.0.x or 10.x (note: Tomcat 10 uses Jakarta EE instead of Java EE, so ensure your dependencies align)
  Compare the Tomcat version on your Linux server with what’s documented for your Spring Boot version—mismatches often cause silent deployment failures.

Linux permissions are a common culprit here:

• Tomcat runs under a dedicated user (usually tomcat), so make sure your WAR file and the auto-extracted folder in webapps have the right ownership and permissions:

  chown -R tomcat:tomcat /path/to/your/tomcat/webapps
  chmod -R 755 /path/to/your/tomcat/webapps
  

• Also check if the server has enough disk space on the partition where webapps is located—run df -h to confirm no partitions are full.

You mentioned the server is outputting logs—focus on these key files in Tomcat’s logs directory:

• catalina.out: This captures most startup errors, like missing classes, configuration failures, or database connection issues. Use tail -f /path/to/tomcat/logs/catalina.out to watch logs in real-time as you start Tomcat.
• localhost.log: Contains web app-specific errors, like failed servlet initialization.
• Look for ERROR or WARN entries—these will point directly to issues (e.g., ClassNotFoundException means a dependency isn’t packaged in the WAR, or there’s a conflict with Tomcat’s global libraries).

Local and Linux environments have different defaults—check these:

• Port Configuration: The server.port property in your application.properties/application.yml is ignored by external Tomcat—Tomcat’s server.xml controls the port, so don’t rely on this setting.
• File Paths: Replace Windows-style paths (e.g., D:/data/files) with Linux paths (e.g., /opt/data/files) in your configs.
• External Resources: If your app uses databases, APIs, or file storage, ensure the Linux server has network access to these resources (e.g., check firewall rules for database ports).

• Port Conflicts: Verify Tomcat’s default port (usually 8080) isn’t being used by another process. Run:

  netstat -tulpn | grep 8080
  

  If it’s occupied, either kill the conflicting process or change the port in Tomcat’s conf/server.xml.
• Global Library Conflicts: Tomcat’s lib directory contains global jars—if your WAR includes duplicate jars (e.g., different versions of servlet-api), this can cause classloading errors. Remove conflicting jars from either your WAR or Tomcat’s lib folder.

1. Deploy your WAR to a local Tomcat instance that matches the Linux server’s version—if it fails here, the problem is with the WAR package itself, not the Linux environment.
2. Stop Tomcat on Linux (sh /path/to/tomcat/bin/shutdown.sh), delete the old WAR and extracted folder from webapps, then copy the fresh WAR over and restart Tomcat. Watch the logs closely during startup.

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