-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting error while running sonar scanner with Spotbugs rules for monolithic project ? #361
Comments
It seems I had a similar issue. Applying all findbugs rules into my existing sonarway copy profile.
|
|
I found these logs:
Is there any other info you need for investigation? |
Can you please share the entire log of the sonar analysis? The bits you have shared might be unrelated problems. |
Hi gtoison, thanks a lot for your attention For this out of memory problem, I will try to exclude this class com.sinosoft.utility.Reflections firstly, and sync the result later |
Findbugs Plugin have around 449 rules. Applying all those rules into my existing sonarqube quality profile and started sonar scanning which is taking lots of memory to scan the whole project and also it is throwing error after some time.
I am using Sonarqube version: 7.5 and Spotbugs jar version: 3.9.4
Set SONAR_SCANNER_OPTS=-Xmx10G for Temporary Command Prompt session but facing the issue with Java Heap Space (GC overhead limit exceed)
ERROR: Error during SonarQube Scanner execution
ERROR: Can not execute Findbugs
ERROR: Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
ERROR: Caused by: GC overhead limit exceeded
ERROR:
ERROR: Re-run SonarQube Scanner using the -X switch to enable full debug logging.
I expect sonar scanner to work successfully with some selected Spotbugs(Findbugs) rule like vulnerabilities and Malicious rule but its didn't work for limited rule also.
The text was updated successfully, but these errors were encountered: