SonarQube server error

Hi, Request you to help with below mentioned error. I am unable to start the server as it says referring to a deprecated method.

  • Using SonarQube Server 9.9 LTA version
  • SonarQube is deployed: in zip format
  • what are you trying to achieve - trying to start the server (StartSonar.bat)

Logs pasted below -

Starting SonarQube…
2024.12.12 12:50:48 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\sonarqube\sonarqube-9.9.8.100196\temp
2024.12.12 12:50:48 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:54983]
2024.12.12 12:50:48 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\sonarqube\sonarqube-9.9.8.100196\elasticsearch]: C:\Program Files\Zulu\zulu-17\bin\java -XX:+UseG1GC -Djava.io.tmpdir=C:\sonarqube\sonarqube-9.9.8.100196\temp -XX:ErrorFile=C:\sonarqube\sonarqube-9.9.8.100196\logs\es_hs_err_pid%p.log -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djna.tmpdir=C:\sonarqube\sonarqube-9.9.8.100196\temp -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j2.formatMsgNoLookups=true -Djava.locale.providers=COMPAT -Dcom.redhat.fips=false -Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=C:\sonarqube\sonarqube-9.9.8.100196\elasticsearch -Des.path.conf=C:\sonarqube\sonarqube-9.9.8.100196\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
2024.12.12 12:50:50 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.12.12 12:51:05 INFO app[o.s.a.SchedulerImpl] Process[es] is up
2024.12.12 12:51:05 INFO app[o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\sonarqube\sonarqube-9.9.8.100196]: C:\Program Files\Zulu\zulu-17\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\sonarqube\sonarqube-9.9.8.100196\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 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-9.9.8.100196.jar;C:\sonarqube\sonarqube-9.9.8.100196\lib\jdbc\h2\h2-2.1.214.jar org.sonar.server.app.WebServer C:\sonarqube\sonarqube-9.9.8.100196\temp\sq-process13234949780142782690properties
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/C:/sonarqube/sonarqube-9.9.8.100196/lib/sonar-application-9.9.8.100196.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
2024.12.12 12:51:10 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped
2024.12.12 12:51:10 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.12.12 12:51:10 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

That’s a bit of a red herring. It looks like the Web Server stops, unrelated to that message.

What do the other logs say?

there’s a deprecated method in java which is been referenced while starting SonarQube which is why it’s failing to start I guess. There is no change in the setup which could lead to this. Thanks!

This is a non-fatal warning. There are 4 log files in total, what do the others say?