Why Am I Seeing Error "CC.00130044.400 Execute source plugin failed"?

Symptom

• If the log contains "The agent has not been fully initialized yet" or "Some unexpected problems occurred while executing the SecsolarPlugin", the engine task fails to be executed. Resolve the issue according to the instructions provided in this section.
• If the log contains "ERROR during SonarScanner execution", the compilation fails due to the file format. Resolve the issue by referring to Compilation Error Due to File Format.

Cause Analysis

• Too many rules in the rule set are used.
• Checking an excessively large amount of code may cause the executors to run out of memory.
• If a large amount of JavaScript, TypeScript, or CSS code is involved, the check process may exceed the available Node.js memory.

Solution

If the JavaScript, TypeScript, or CSS language is checked and the log contains "ERROR The analysis will stop due to the Node.js process running out of memory (heap size limit xxxx MB)", perform the following operations:

• xxxx indicates the default heap memory limit. In this case, you can add a file named sonar-project.properties to the root directory of the code repository and write sonar.javascript.node.maxspace=8192 to the file. This indicates that the default heap memory limit is 8 GB. (The value must be greater than xxxx in the error description, not necessarily 8 GB.)

Use any of the following methods to reduce the code in a task:

• Split the task into multiple tasks and set rule sets in different languages for them. For details about how to set a rule set, see Configuring a Rule Set.

  For example, to check code in multiple languages, such as Java, C, and C#, within task A, split the task into tasks A1, A2, and A3, and set the Java, C, and C# rule sets, respectively.

• Split the task into multiple tasks, exclude some files from the split tasks, and then check the code. For details about how to exclude files, see Configuring Check Scope.

  For example, split task A into tasks A1, A2, and A3, and set them to check only file 1, file 2, and file 3, respectively.

• Split the code repository used by the task into multiple sub-repositories, create tasks respectively, and check the code.