CODEWITHSUNDEEP
tomcattfssonarqubesonar-runnersonarqube-scan
Alexandre Parent
Alexandre Parent

Reputation: 31

SonarQube 5.6.1 report upload fail if size > 20 megabytes 404 error code

I successfully setup a sonar qube instance with a team foundation server/vNext on windows server. *this is a different problem then sqube 6.0/6.1 and the connectorj problem.

Some of our projects generate reports of size greater than 20 megabytes and at upload time we get a 404 error from sonar qube. Since all other projects works fine and only those who generate > 20m reports, I suspect the maxPostSize param in Tomcat but everything is embedded in .jars so I'm not sure how to double check it. In github, the connector seems correctly set to -1 (infinite post size). In the mbean descriptor of tomcat (org/apache/catalina/connector/mbeans-descriptors.xml), the attribute max post size is defined but without a default value.

Error in question :

Analysis reports compressed in 15547ms, zip size=34 MB

EXECUTION FAILURE
Total time: 13:56.691s
Final Memory: 67M/574M
Error during SonarQube Scanner execution


org.sonarqube.ws.client.HttpException: Error 404 on https://sonarqube.company.com/api/ce/submit?projectKey=good_project_key&projectName=good_project_name

[error]at org.sonarqube.ws.client.BaseResponse.failIfNotSuccessful(BaseResponse.java:34)
[error]at org.sonar.batch.bootstrap.BatchWsClient.failIfUnauthorized(BatchWsClient.java:99)
[error]at org.sonar.batch.bootstrap.BatchWsClient.call(BatchWsClient.java:69)
[error]at org.sonar.batch.report.ReportPublisher.upload(ReportPublisher.java:172)

Upvotes: 3

Views: 2708

Answers (1)

Nicolas B.
Nicolas B.

Reputation: 7331

You seem to be using an HTTPS URL for your SonarQube, which means that you're contacting it through a reverse-proxy. Since you're on Windows then (I guess) you might be using Microsoft IIS, in which case double-check your file upload limits in IIS.

If another proxy: double-check its file upload limits likewise.

Upvotes: 11

Related Questions