Starten Sie Spring-Boot 3.1 auf Heroku mit Tomcat 10.1 ⇐ Java

[Anonymous]

Ich setze einen Spring-Boot V3.1 und Java 21 auf Heroku ein. Standardmäßig schlagen Heroku Tomcat 9.0.3 vor. Ich kann Tomcat 10.1 nicht einschalten, was für mein Projekt benötigt wird.

Code: Select all

org.apache.maven.plugins
maven-dependency-plugin


package
copy



com.heroku
webapp-runner
10.1.34.0
webapp-runner.jar






< /code>
Ich aktualisiere meine Procfile < /p>
web: java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port $PORT target/monsuivi-app.war
< /code>
Verwenden von Maven Clean Paket Ich erstelle eine Kriegsdatei und verwende dann den Befehl heroku cli, um auf Heroku Server hochzuladen. < /p>
remote: -----> Building on the Heroku-24 stack
remote: -----> Using buildpack: heroku/jvm
remote: -----> JVM Common app detected
remote: -----> Installing Azul Zulu OpenJDK 21.0.6
remote: -----> Discovering process types
remote:        Procfile declares types -> web
remote:
remote: -----> Compressing...
remote:        Done: 143.7M
remote: -----> Launching...
remote:        Released v20
remote:        https://monsuivi-XXXXXX-XXXX.herokuapp.com/ deployed to Heroku
remote:
-----> Done

< /code>
Auf Heroku -Protokoll Ich sehe den Server, der gestartet wird, aber immer noch mit Tomcat 9.0.30. < /p>
2025-04-01T19:46:49.727953+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2025-04-01T19:46:49.730841+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -XX:MaxRAM=536870912 -Xmx300m -Xss512k -XX:CICompilerCount=2
2025-04-01T19:46:50.236505+00:00 app[web.1]: Expanding monsuivi-app.war into /app/target/tomcat.28055/webapps/expanded
2025-04-01T19:46:50.236540+00:00 app[web.1]: Adding Context  for /app/target/tomcat.28055/webapps/expanded
2025-04-01T19:46:50.442914+00:00 app[web.1]: Apr 01, 2025 7:46:50 PM org.apache.coyote.AbstractProtocol init
2025-04-01T19:46:50.442916+00:00 app[web.1]: INFO: Initializing ProtocolHandler ["http-nio-28055"]
2025-04-01T19:46:50.457600+00:00 app[web.1]: Apr 01, 2025 7:46:50 PM org.apache.catalina.core.StandardService startInternal
2025-04-01T19:46:50.457602+00:00 app[web.1]: INFO: Starting service [Tomcat]
2025-04-01T19:46:50.457853+00:00 app[web.1]: Apr 01, 2025 7:46:50 PM org.apache.catalina.core.StandardEngine startInternal
2025-04-01T19:46:50.457854+00:00 app[web.1]: INFO: Starting Servlet engine: [Apache Tomcat/9.0.30]
2025-04-01T19:46:50.638337+00:00 app[web.1]: Apr 01, 2025 7:46:50 PM org.apache.catalina.startup.ContextConfig getDefaultWebXmlFragment
2025-04-01T19:46:50.638346+00:00 app[web.1]: INFO: No global web.xml found
2025-04-01T19:46:50.660451+00:00 app[web.1]: Apr 01, 2025 7:46:50 PM org.apache.tomcat.util.descriptor.web.WebXml setVersion
2025-04-01T19:46:50.660452+00:00 app[web.1]: WARNING: Unknown version string [5.0]. Default version will be used.
2025-04-01T19:46:50.914619+00:00 heroku[web.1]: State changed from starting to up
2025-04-01T19:46:53.476052+00:00 app[web.1]: Apr 01, 2025 7:46:53 PM org.apache.jasper.servlet.TldScanner scanJars
2025-04-01T19:46:53.476067+00:00 app[web.1]: INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
2025-04-01T19:46:53.510613+00:00 app[web.1]: Apr 01, 2025 7:46:53 PM org.apache.coyote.AbstractProtocol start
2025-04-01T19:46:53.510615+00:00 app[web.1]: INFO: Starting ProtocolHandler ["http-nio-28055"]
````
if you can help
Brgds
cyrille