Issue during Sonar Scan

Hi,

We are facing some issues while sonar scan of one of our internal application. We are using sonarqube 7.7 version which is running over the docker along with postgres SQL container. Sonar build works fine but at the end it creates report and throws below exception,

[INFO] Sensor Zero Coverage Sensor
[INFO] Sensor Zero Coverage Sensor (done) | time=2349ms
[INFO] Sensor Java CPD Block Indexer
[INFO] Sensor Java CPD Block Indexer (done) | time=1476ms
[INFO] SCM provider for this project is: git
[INFO] 218 files to be analyzed
[INFO] 218/218 files analyzed
[INFO] 289 files had no CPD blocks
[INFO] Calculating CPD for 1125 files
[INFO] CPD calculation finished
[INFO] Analysis report generated in 7147ms, dir size=15 MB
[INFO] Analysis report compressed in 5522ms, zip size=6 MB
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:09 min
[INFO] Finished at: 2019-11-29T18:56:06+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project ProjectParent: Fail to request http://IP:9000/api/ce/submit?projectKey=com.org.projectname%3ParentProject&projectName=ParentProject: timeout: Socket closed -> [Help 1]

Please let us know how the above issue can be fixed. Any leads will be appreciated.

Thanks and regards,
Rushil Jain

Hi Rushil,

Welcome to the community!

You need to check whatever’s on your network between Jenkins and SonarQube. You probably have a request size limit set too low in your proxy.

 
HTH,
Ann

Thanks for the help Ann. But, could you please tell me that where i need to check the request size limit? I mean, its from Machine level or Application level.

regards,
Rushil Jain

Hi Rushil,

This lies outside my area of expertise so I can’t tell you more than that you need to talk to your network folks.

 
Ann