Payload Too Large

SonarQube
, ,
1

Sonarqube 7.9.5 LTS, SonarCSS 1.2

Hello everyone,

When we try to analyze a project on Azure Devops as part of the pipeline, we’re getting an error stating that payload is too large. This started to occur after upgrading the SonarQube version from 7.5 to 7.9.5LTS(Meanwhile we also updated Java too). But seems like mostly related with SonarCSS plugin.

That issue seems similar to what is addressed here; Increase the limit for request size · Issue #251 · SonarSource/sonar-css · GitHub
But seems like SonarCSS isn’t release 1.3 yet. Any workarounds for this until that comes?
Or could this be related to anything else?

 { PayloadTooLargeError: request entity too large
 { PayloadTooLargeError: request entity too large
     at readStream (C:\****\.scannerwork\css-bundle\node_modules\raw-body\index.js:155:17)
     at getRawBody (C:\****\.scannerwork\css-bundle\node_modules\raw-body\index.js:108:12)
     at read (C:\****\.scannerwork\css-bundle\node_modules\body-parser\lib\read.js:77:3)
     at jsonParser (C:\****\.scannerwork\css-bundle\node_modules\body-parser\lib\types\json.js:135:5)
     at Layer.handle [as handle_request] (C:\****\.scannerwork\css-bundle\node_modules\express\lib\router\layer.js:95:5)
     at trim_prefix (C:\****\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:317:13)
     at C:\****\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:284:7
     at Function.process_params (C:\****\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:335:12)
     at next (C:\****\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:275:10)
     at expressInit (C:\****\.scannerwork\css-bundle\node_modules\express\lib\middleware\init.js:40:5)
 message: 'request entity too large',
 expected: 167037,
 length: 167037,
 limit: 102400,
 type: 'entity.too.large' }

Thanks.

2

Hi,

Welcome to the community!

Could you provide the content of your logs up to the error?

 
Ann

3

We had the same issue. In our case, the build was happening on a different machine, which was accessing the SQ server through IIS. Increasing the max transfer size in the IIS configuration fixed it. (But YMMV…)

1 Like