Sonar Stopped : WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecur

SonarQube Server / Community Build
1

Sonar Stopped giving a warning

WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/opt/sonarqube-9.9.1.69595/lib/sonar-application-9.9.1.69595.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release

Sonar version - 9.9.1.69595
Deployed on on premise using zip file

2

Hi,

This warning is not a cause for the SonarQube server to stop. You’ll need to check all log files.

3

Thanks Felipe for going through the issue

I saw there were no errors in sonar.log, web.log, es.log but getting this warning in web.log

2023.08.21 11:43:58 INFO web[o.s.p.ProcessEntryPoint] Hard stopping process
2023.08.21 11:43:58 INFO web[o.s.s.n.NotificationDaemon] Notification service stopped
2023.08.21 11:43:58 INFO web[c.z.h.HikariDataSource] HikariPool-1 - Shutdown initiated…
2023.08.21 11:43:58 INFO web[c.z.h.HikariDataSource] HikariPool-1 - Shutdown completed.
2023.08.21 11:43:58 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [OkHttp TaskRunner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@17.0.6/java.lang.Object.wait(Native Method)\n java.base@17.0.6/java.lang.Object.wait(Object.java:472)\n app//okhttp3.internal.concurrent.TaskRunner$RealBackend.coordinatorWait(TaskRunner.kt:294)\n app//okhttp3.internal.concurrent.TaskRunner.awaitTaskToRun(TaskRunner.kt:218)\n app//okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:59)\n java.base@17.0.6/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)\n java.base@17.0.6/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)\n java.base@17.0.6/java.lang.Thread.run(Thread.java:833)
2023.08.21 11:43:58 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [Okio Watchdog] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@17.0.6/java.lang.Object.wait(Native Method)\n java.base@17.0.6/java.lang.Object.wait(Object.java:472)\n app//okio.AsyncTimeout$Companion.awaitTimeout$okio(AsyncTimeout.kt:318)\n app//okio.AsyncTimeout$Watchdog.run(AsyncTimeout.kt:183)

4

Hi @yashvanth ,

Can you attach the full set of logs from $SQ_HOME/logs here for us to review? It’s hard to review only a snippet of the log so we need to see the full context of what could cause your problem.

5

Hi it seems I am facing the same issue and this thread does not seem to have been resolved can you please check the log files content i providing
it seems some issue with elasticsearch number of requests still any guidance to resolve this will be helpful which can be found in web.log file
access.log (1.9 KB)
es.log (10.5 KB)
sonar.log (3.0 KB)
web.log (2.5 MB)

6

Hi @soumyamitra ,

Apologies for the long delay. Your ES log show the error:

2024.05.28 14:42:39 WARN  es[][o.e.c.r.a.DiskThresholdMonitor] flood stage disk watermark [95%] exceeded on [zvBdi-Z4RZe9GDSm2j8wiA][sonarqube][C:\Users\Administrator\Downloads\sonarqube-9.9.5.90363\data\es7\nodes\0] free: 1.1gb[1.4%], all indices on this node will be marked read-only

See Troubleshooting for more information on how to fix this issue. Basically, you need to ensure enough disk space and then delete the ES indexes:

  1. Ensure enough disk space is available
  2. Stop SonarQube
  3. Delete the data/es7 (data/es8 if you are on SQ 10.x) directory
  4. Restart SonarQube