Hi,
We recently upgraded from SonarQube version 7.9.1 community edition to version 8.9.10 enterprise edition and deployed it via the .zip file from downloads section on sonarsource.
Upon release documentation I copied over the memory allocations from sonar.properties on version 7.9.1 manually over to version 8.9.10. Using SQLServer DB.
We have a gradle built application via cloudbees jenkins that has approx 400k LOC and the sonarqube task is failing due to the error “Expiring Daemon because JVM heap space is exhausted”, “Daemon will be stopped at the end of the build after running out of JVM memory”.
I have tried increasing the workers but only slows it down even more.
Below are the existing memory allocations for Web & Compute Engine that I have set on SonarQube version 8.9.10 enterprise edition.
sonar.web.javaOpts=-Xmx1024m -Xms512m -XX:+HeapDumpOnOutOfMemoryError
sonar.ce.javaOpts=-Xmx2048m -Xms512m -XX:+HeapDumpOnOutOfMemoryError
FYI, This issue was not happening on version community edition 7.9.1.
Any help would be appreciated.
Thanks,
Brendan