Jvm 1 | WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) - Developer Edition 9.2.4
  • what are you trying to achieve - Want to setup SonarQube for my iOS project
  • what have you tried so far to achieve this
    On Mac sh /Applications/SonarQube/bin/macosx-universal-64/sonar.sh console

Error :

IN-FVFZR6QRL410:~ santoshsingh$ sh /Applications/SonarQube/bin/macosx-universal-64/sonar.sh console
Running SonarQube...
wrapper  | --> Wrapper Started as Console
wrapper  | Launching a JVM...
jvm 1    | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1    |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
jvm 1    | 
jvm 1    | 2022.01.15 22:18:13 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /Applications/SonarQube/temp
jvm 1    | 2022.01.15 22:18:13 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:49828]
jvm 1    | 2022.01.15 22:18:13 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/Applications/SonarQube/elasticsearch]: /Applications/SonarQube/elasticsearch/bin/elasticsearch
jvm 1    | 2022.01.15 22:18:13 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1    | 2022.01.15 22:18:37 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
jvm 1    | 2022.01.15 22:18:37 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/Applications/SonarQube]: /usr/local/Cellar/openjdk/17.0.1/libexec/openjdk.jdk/Contents/Home/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/Applications/SonarQube/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.2.4.50792.jar:/Applications/SonarQube/lib/jdbc/h2/h2-1.4.199.jar org.sonar.server.app.WebServer /Applications/SonarQube/temp/sq-process14675572689801682992properties
jvm 1    | WARNING: A terminally deprecated method in java.lang.System has been called
jvm 1    | WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/Applications/SonarQube/lib/sonar-application-9.2.4.50792.jar)
jvm 1    | WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
jvm 1    | WARNING: System::setSecurityManager will be removed in a future release
jvm 1    | 2022.01.15 22:18:43 INFO  app[][o.s.a.SchedulerImpl] Process[web] is stopped
jvm 1    | 2022.01.15 22:18:43 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 143
jvm 1    | 2022.01.15 22:18:43 INFO  app[][o.s.a.SchedulerImpl] Process[es] is stopped
jvm 1    | 2022.01.15 22:18:43 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
wrapper  | <-- Wrapper Stopped
2

Hey there.

I’d bet you’re starting SonarQube with a higher version of Java than is supported. As noted in the requirements, you should stick to Java 11.

3

Sonarqube 9.9 LTS requires JDK17, so this message is displayed with the latest build on OpenJDK17.

Should we just ignore this for now / is there a fix expected?

4

You should just ignore it for now, as it’s harmless – I don’t expect a fix for this version, but I will flag it for attention in case internal teams aren’t aware.

And, in this post from last year, the warning was likely not the root cause of their server failing to start.