Troubleshooting the analysis

If your SonarQube 10.4 analysis errors out.

For AI agents: You're in the SonarQube Server 10.4 documentation. For a list of all 10.4 pages, see the SonarQube Server 10.4 page index. For the whole site, see the page index or the full text. For another version, replace 10.4 in the URL with that version. The latest version has no version number in its URL.

See also the Troubleshooting section on the corresponding Scanner page.

Out of memory error

If your analysis errors out with java.lang.OutOfMemoryError: GC overhead limit exceeded then it means that your project is too large or too intricate for the scanner to analyze with the default memory allocation. To fix this you’ll want to allocate a larger heap (using -Xmx[numeric value here]) to the process running the analysis. Some CI engines may give you an input to specify the necessary values, for instance if you’re using a Maven Build Step in a Jenkins job to run analysis. Otherwise, use Java Options to set a higher value. Note that details of setting Java Options are omitted here because they vary depending on the environment.

PKIX path building failed

If your analysis errors out with PKIX path building failed then it means that your SonarQube server is configured with HTTPS and a self-signed SSL certificate (see Securing the server behind a proxy in Operating the server). However, the certificate is not correctly configured in the scanner machine’s JVM. This configuration is outside of SonarQube scope. The server certificate is unknown and could not be validated with the provided truststore. To solve the issue, you need to Installing the server’s self-signed certificate. See Oracle’s documentation for more information.