Sonar Scan stuck in rule: S5135, entrypoints: 50

Report a bug
#1

Hi, I’m having a particular issue with SonarScanner executed in Jenkins stage, the scan got stuck for hours at the following line

[sonar:sonar] rule: S5135, entrypoints: 50

Version used: 8.1.0.31237 Developer Edition
Potential workaround: I stop the Jenkins job and retry it again, sometime passes but other got stuck.

Is there a way to solve this issue by tunning the agent where sonarscanner is executed, or a fix from the SonarQube server?

Attached some images for references.

Thanks.

image sonar_stage

#2

Hello,

A lot of perf improvements were made on this component since the v8.1.
So the best advice I can share is to upgrade to SonarQube 8.4 that was just released.

If you still have the same problem with 8.4, then we will need more details such as a zip file of the UCFGs directory so that we can try to reproduce the problem locally.

Regards
Alex

#3

Hello Alexandre

Thanks for your reply, I’ll do the upgrade and if I have the same issue, will communicate back with the necessary files.

Regards,
Romell

#4

Hi Alexandre, the upgrade solved the issue thanks a lot.

#5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.