部署Spring Boot应用至Heroku时遭遇H10错误，本地运行正常

Hey there, let's work through that frustrating H10 error on Heroku—since your app runs fine in Eclipse and via executable JAR, the issue is almost certainly related to how Heroku is trying to run or configure your app. Here are the most common fixes to try:

1. Ensure You're Using Heroku's Dynamic Port #

Heroku assigns a dynamic port to your app at runtime, so hardcoding a port like 8080 will trigger the H10 error. You need to read the PORT environment variable provided by Heroku, with a fallback for local testing.

For a Java/Spring Boot app, update your configuration:

• In application.properties:

  server.port=${PORT:8080}
  

• If you're using a raw Java server (like embedded Tomcat), fetch the port in your code:

  String port = System.getenv("PORT");
  int serverPort = (port != null) ? Integer.parseInt(port) : 8080;
  

2. Verify Your Procfile is Correct #

Heroku uses the Procfile to know how to start your app. Make sure it's in the root of your repository, named exactly Procfile (no file extension), and has the right command for your JAR:

web: java -jar target/your-app-filename.jar

Double-check the path to your JAR—if you're using Maven, it's usually in the target folder; for Gradle, it's build/libs.

3. Dig Into Heroku's Logs for Details #

The H10 error is a generic "app crashed" message, so the real issue is hidden in the logs. Use the Heroku CLI to view real-time logs:

heroku logs --tail

Look for clues like:

• Missing environment variables (e.g., database URLs you have locally but haven't set on Heroku)
• Dependency conflicts or missing JARs
• Runtime exceptions during app startup (like failed database connections)

4. Check for Startup Timeouts #

Heroku expects your app to start within 60 seconds. If your app takes too long to initialize (e.g., loading large datasets, slow external API calls), it will crash with H10. Try:

• Delaying initialization of non-critical components until after the app starts
• Optimizing dependency loading (ensure all dependencies are packaged in your JAR)
• Using web: java -XX:+UseParallelGC -jar your-app.jar to speed up JVM startup

5. Match Java Versions Between Local and Heroku #

A mismatch in Java versions can cause unexpected crashes. Create a system.properties file in your repo root to specify the exact version you're using locally:

java.runtime.version=17

Replace 17 with your local Java version (check with java -version).

Start with the first two steps—port configuration and Procfile issues are the most common culprits. Once you fix those, the logs should point you to any remaining problems.

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