9.8 to 9.9 upgrade. Webserver failing to start

That’s definitely not on the “OS side”.
The reason of the issue could be connected to the JDK version.
As soon as I restored backup with SonarQube 9.8 and configured environment variables to point to openjdk version “11.0.13” service started successfully and web.log and all other log files were created. But when I changed environments to point to openjdk version “17.0.2” SonarQube 9.8 started and stopped after creating only two log files es.log and sonar.log with the same lines in sonar.log as before -

2023.02.28 17:03:15 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.02.28 17:03:30 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2023.02.28 17:03:30 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\SonarQube\sonarqube-9.8.0.63668]: C:\SonarQube\JDK\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=c:\SonarQube\SonarHome\temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -Dcom.redhat.fips=false -server -Xmx768m -Xms256m -XX:MaxPermSize=160m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-9.8.0.63668.jar;C:\SonarQube\sonarqube-9.8.0.63668\lib\jdbc\mssql\mssql-jdbc-10.2.1.jre11.jar org.sonar.server.app.WebServer c:\SonarQube\SonarHome\temp\sq-process15730836310318985955properties
2023.02.28 17:03:30 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [Web Server]: 1
2023.02.28 17:03:30 INFO  app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2023.02.28 17:03:30 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.02.28 17:03:30 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

So we can assume that Web Server of SonarQube 9.9 failing to start on openjdk version “17.0.2” due to some unknown issue. What can I do to fix that?