Start Free
10.6 | Analyzing source code | Troubleshooting the analysis

Was this page helpful?

Troubleshooting the analysis

On this page

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.

You can also add an exclusion to manage the files and folders you don't need to analyze by limiting your Analysis scope. Additionally, using a Solid-state drive or something similar will help speed up the analysis process and thus use less memory, especially for small file access.

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 import the SonarQube server certificate to the Java truststore. See Oracle's documentation for more information.

Various error messages

The format of the analysis property sonar.token= is invalid

You may encounter this issue when using SONAR_TOKEN as a secret in a calling workflow in GitHub in case the called workflow doesn't manage to read it as a secret. In that case, make sure that the secret is inherited from the calling workflow (you may use the secrets: inherit keyword). See GitHub documentation for more information.

The maximum number of open files was reached

On a Linux system, see Configuring the maximum number of open files and other limits in Pre-installation steps on Linux.

On a MacOS system, see Configuring the maximum number of open files in Pre-installation steps on macOS.

Error when analyzing files with non-ASCII characters in the name

When analyzing files with non-ASCII characters in the name, if the Malformed input or input contains unmappable characters error is raised then you should make sure that the environment variables LC_ALL and LANG are properly set before running the analysis as shown below.

export LC_ALL="en_US.UTF-8"
export LANG="en_US.UTF-8"

© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARLINT, SONARQUBE, SONARCLOUD, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Creative Commons License