基于webapp-runner部署到Heroku的Java Web应用启动崩溃求助

Hey there, let's work through why your app is crashing on Heroku even though it runs fine locally with Tomcat. I'll walk you through common issues and fixes based on your setup:

1. Verify Webapp-Runner Dependency Configuration #

First, make sure your Maven project is correctly pulling and packaging the webapp-runner jar. If this jar is missing from target/dependency, your Procfile command will fail immediately.

Check your pom.xml for these critical configurations:

• Dependency for webapp-runner: Match the version to your local Tomcat version (e.g., use 9.x runners for Tomcat 9):

<dependency>
    <groupId>com.github.jsimone</groupId>
    <artifactId>webapp-runner</artifactId>
    <version>9.0.70.0</version>
    <scope>provided</scope>
</dependency>

• Maven Dependency Plugin: This ensures the runner is copied to target/dependency during the package phase:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-dependency-plugin</artifactId>
    <executions>
        <execution>
            <phase>package</phase>
            <goals>
                <goal>copy</goal>
            </goals>
            <configuration>
                <artifactItems>
                    <artifactItem>
                        <groupId>com.github.jsimone</groupId>
                        <artifactId>webapp-runner</artifactId>
                        <version>9.0.70.0</version>
                        <destFileName>webapp-runner.jar</destFileName>
                    </artifactItem>
                </artifactItems>
            </configuration>
        </execution>
    </executions>
</plugin>

2. Refine Your Procfile Command #

Your current Procfile looks mostly right, but there are a few tweaks to avoid ambiguity:

• Specify the exact WAR file name: If your build produces a WAR with a version suffix (e.g., myapp-1.0.war), using target/*.war might cause issues if old builds linger. Replace it with the full name:

  web: java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port $PORT target/myapp-1.0.war
  

• Add --expand-war for better compatibility: Some apps fail when running directly from the WAR; forcing expansion can resolve classpath or resource loading issues:

  web: java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port $PORT --expand-war target/myapp-1.0.war
  

3. Get More Detailed Logs to Diagnose the Crash #

If you can't spot the issue in default logs, crank up the verbosity:

• Stream real-time logs with Heroku CLI:

  heroku logs --tail
  

• Add JVM debug flags to your Procfile to track class loading or memory issues:

  web: java $JAVA_OPTS -verbose:class -Xmx512m -jar target/dependency/webapp-runner.jar --port $PORT target/*.war
  

  The -verbose:class flag will log every class loaded, which can reveal missing dependencies or version conflicts.

4. Align JDK Versions and Resource Limits #

Heroku's default JDK might differ from your local setup, causing compatibility issues:

• Enforce JDK version in pom.xml: Use the maven-compiler-plugin to match your local JDK (replace 1.8 with your version, e.g., 11):

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>3.8.1</version>
    <configuration>
        <source>1.8</source>
        <target>1.8</target>
    </configuration>
</plugin>

• Adjust memory settings: Heroku has strict memory limits; if your app runs out of memory on startup, add these flags to JAVA_OPTS:

  web: java $JAVA_OPTS -Xmx512m -XX:MaxMetaspaceSize=256m -jar target/dependency/webapp-runner.jar --port $PORT target/*.war
  

5. Simulate Heroku's Environment Locally #

The fastest way to debug is to replicate the Heroku run command on your machine:

1. Run mvn package to build your WAR and copy dependencies.
2. Execute the exact command from your Procfile (replace $PORT with a local port like 8080):

   java -jar target/dependency/webapp-runner.jar --port 8080 target/*.war
   

If this crashes locally, you can use your IDE's debugger to step through the startup process and pinpoint the issue.

Start with these steps—most Heroku deployment crashes for Java apps boil down to dependency mismatches, configuration gaps, or resource limits.

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