Sonarqube ver 10 stops

SonarQube Server / Community Build
1

Hi,

Sonarqube running locally stops. It was working before this is the error it shows,

C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\bin\windows-x86-64>StartSonar.bat
Starting SonarQube...
2023.04.22 07:30:23 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\temp
2023.04.22 07:30:23 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:60088]
2023.04.22 07:30:23 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\elasticsearch]: C:\Program Files\Java\jdk-17\bin\java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\elasticsearch -Des.path.conf=C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\temp\conf\es -Des.distribution.type=tar -cp C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\elasticsearch\lib\*;C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\elasticsearch\lib\cli-launcher\* org.elasticsearch.launcher.CliToolLauncher
2023.04.22 07:30:23 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.04.22 07:30:36 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2023.04.22 07:30:36 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432]: C:\Program Files\Java\jdk-17\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\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-10.0.0.68432.jar;C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\lib\jdbc\h2\h2-2.1.214.jar org.sonar.server.app.WebServer C:\sonarqube-10.0.0.68432\sonarqube-10.0.0.68432\temp\sq-process3448589329422398013properties
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-10.0.0.68432/sonarqube-10.0.0.68432/lib/sonar-application-10.0.0.68432.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
2023.04.22 07:30:38 INFO  app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2023.04.22 07:30:38 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.04.22 07:30:38 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped.

Any help to resolve this issue is appreciated.

Thank you,

2

Good morning @sandeepmalla

did you just upgrade SonarQube and are using MSSQL as database server? Then it might be that you need to add a parameter to your configuration, see Issues upgrading from 9.7.0.

1 Like
3

Thank you, Volker for the reply. It wasn’t the upgrade. I had installed SonarQube 10. I guess it conflicted with the newer java version. I later installed in the system. I resolved the issue by removing that java version and deleting the old SonarQube folder with a new one. It works now. Thanks once again.