what have you tried so far to achieve this:
** restarting the service
** restarting the VM
** recreated the Elastic search data folder
After the VM was patched over the weekend, we noticed NO projects are being displayed at the main page.
The project data are there, just not showing by default.
The projects will only display if we choose a filter, like selecting a particular quality gate: Failed/Passed.
We have tried different ways (see above), including the searched answered in this forum by stopping the service, then delete the elastic search data folder, then start the service again.
Some of the projects will show if we click “Failed”/“Passed” filter of Quality Gate. But just none shows in the main page / dashboard.
Nothing really stands out with regards to errors etc. in the logs, except for the following 1 error log only:
2023.07.26 08:57:24 INFO ce[AYmPRUUXLzQhrDAK2IIt][o.s.c.t.s.ComputationStepExecutor] Index analysis | status=SUCCESS | time=2922ms
2023.07.26 08:57:24 INFO ce[AYmPRUUXLzQhrDAK2IIt][o.s.c.t.s.ComputationStepExecutor] Update need issue sync for branch | status=SUCCESS | time=0ms
2023.07.26 08:57:24 INFO ce[AYmPRUUXLzQhrDAK2IIt][o.s.c.t.s.ComputationStepExecutor] Compute total Project ncloc | status=SUCCESS | time=15ms
2023.07.26 08:57:24 WARN ce[AYmPRUUXLzQhrDAK2IIt][o.s.c.t.p.s.PersistPushEventsStep] Error during publishing push event
java.lang.NullPointerException: Cannot invoke "org.sonar.ce.task.projectanalysis.component.Component.getName()" because "component" is null
at org.sonar.ce.task.projectanalysis.pushevent.PushEventFactory.raiseSecurityHotspotClosedEvent(PushEventFactory.java:196)
at org.sonar.ce.task.projectanalysis.pushevent.PushEventFactory.raiseSecurityHotspotEvent(PushEventFactory.java:107)
at org.sonar.ce.task.projectanalysis.pushevent.PushEventFactory.raiseEventOnIssue(PushEventFactory.java:79)
at org.sonar.ce.task.projectanalysis.step.PersistPushEventsStep.execute(PersistPushEventsStep.java:63)
at org.sonar.ce.task.step.ComputationStepExecutor.executeStep(ComputationStepExecutor.java:79)
at org.sonar.ce.task.step.ComputationStepExecutor.executeSteps(ComputationStepExecutor.java:70)
at org.sonar.ce.task.step.ComputationStepExecutor.execute(ComputationStepExecutor.java:57)
at org.sonar.ce.task.projectanalysis.taskprocessor.ReportTaskProcessor.process(ReportTaskProcessor.java:75)
at org.sonar.ce.taskprocessor.CeWorkerImpl$ExecuteTask.executeTask(CeWorkerImpl.java:212)
at org.sonar.ce.taskprocessor.CeWorkerImpl$ExecuteTask.run(CeWorkerImpl.java:194)
at org.sonar.ce.taskprocessor.CeWorkerImpl.findAndProcessTask(CeWorkerImpl.java:160)
at org.sonar.ce.taskprocessor.CeWorkerImpl$TrackRunningState.get(CeWorkerImpl.java:135)
at org.sonar.ce.taskprocessor.CeWorkerImpl.call(CeWorkerImpl.java:87)
at org.sonar.ce.taskprocessor.CeWorkerImpl.call(CeWorkerImpl.java:53)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131)
at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:74)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:82)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Ok, your most recent question pointed me to the right direction.
After checking the project keys one by one, I noticed that it might be related to the max length of a url is allowed by the browser.
We have about 38 projects and the total length of the full url exceeds 2110 characters. If I remove one of the project keys from the url and it goes below 2100 characters, it is working fine.
Where can we set the max url length in SonarQube web server?
We tried to reproduce that on Windows + Edge with no luck.
From the investigation that I did looks like when Edge became Chromium-based (2020) the issue is gone. Can you please tell me which version of Edge you have?