Sonar Scanner Web Service Timeout still produces write timeout

dherges · December 1, 2021, 11:38am

Version of Sonar Scanner used: org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar

This is an older version, but newest sonar scanner has same behaviour afaik. We experience write timeout

We have set “sonar.ws.timeout=3600”. The error message from maven is ‘timeout: Software caused connection abort: socket write error’:

[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project foobar: Fail to request url: https://sonarurl/api/ce/submit?projectKey=foobar&projectName=baz&characteristic=branch%3Dfeature%2Fblablubb&characteristic=branchType%3DBRANCH: timeout: Software caused connection abort: socket write error -> [Help 1]

Documentation says:

Maximum time to wait for the response of a Web Service call (in seconds). Modifying this value from the default is useful only when you’re experiencing timeouts during analysis while waiting for the server to respond to Web Service calls.

github.com

SonarSource/sonarqube/blob/08f4eab96ca208faf95770886f9f216293970e85/server/sonar-docs/src/pages/analysis/analysis-parameters.md#web-services

---
title: Analysis Parameters
url: /analysis/analysis-parameters/
---

Project analysis settings can be configured in multiple places. Here is the hierarchy:

* Global properties, defined in the UI, apply to all projects (From the top bar, go to **[Administration > Configuration > General Settings](/#sonarqube-admin#/admin/settings)**)
* Project properties, defined in the UI, override global property values (At a project level, go to **Project Settings > General Settings**)
* Project analysis parameters, defined in a project analysis configuration file or scanner configuration file, override the ones defined in the UI
* Analysis / Command line parameters, defined when launching an analysis (with `-D` on the command line), override project analysis parameters

Note that only parameters set through the UI are stored in the database.
For example, if you override the `sonar.exclusions` parameter via command line for a specific project, it will not be stored in the database. Subsequent analyses, or analyses in SonarLint with connected mode, would still be executed with the exclusions defined in the UI and therefore stored in the DB.

Most of the property keys shown in the interface at both global and project levels can also be set as analysis parameters, but the parameters listed below can _only_ be set at analysis time. 

For language-specific parameters related to test coverage and execution, see [Test Coverage & Execution](/analysis/coverage/).  
For language-specific parameters related to external issue reports, see [External Issues](/analysis/external-issues/).

This file has been truncated. show original

I could imagine the problem is that sonar.ws.timeout is only used for read timeout

OkHttpClientFactory:

github.com

SonarSource/sonar-scanner-commons/blob/103ba603feb871cc5a58c155a8ba9df79862eaa3/api/src/main/java/org/sonarsource/scanner/api/internal/OkHttpClientFactory.java#L75-L81


      
          int readTimeoutSec = DEFAULT_READ_TIMEOUT_SEC;
          if (!System.getProperty(READ_TIMEOUT_SEC_PROPERTY, "").isEmpty()) {
            readTimeoutSec = Integer.parseInt(System.getProperty(READ_TIMEOUT_SEC_PROPERTY));
          }
          
          okHttpClientBuilder.connectTimeout(CONNECT_TIMEOUT_MILLISECONDS, TimeUnit.MILLISECONDS);
          okHttpClientBuilder.readTimeout(readTimeoutSec, TimeUnit.SECONDS);

ScannerWsClientProvider:

github.com

SonarSource/sonarqube/blob/900af07a23832dc8357eb49c3dd997976686ff29/sonar-scanner-engine/src/main/java/org/sonar/scanner/bootstrap/ScannerWsClientProvider.java#L47-L51


      
          String timeoutSec = defaultIfBlank(scannerProps.property(READ_TIMEOUT_SEC_PROPERTY), valueOf(DEFAULT_READ_TIMEOUT_SEC));
          String token = defaultIfBlank(system.envVariable("SONAR_TOKEN"), null);
          String login = defaultIfBlank(scannerProps.property(CoreProperties.LOGIN), token);
          connectorBuilder
            .readTimeoutMilliseconds(parseInt(timeoutSec) * 1_000)

ganncamp · December 8, 2021, 2:18pm

Hi,

There is likely something on your network, e.g. a proxy, that’s blocking the analysis report submission. We’ve seen this behavior vary with other folks by analysis report size; i.e. only payloads over a certain size are blocked. You should check with your network folks.

HTH,
Ann

Topic		Replies	Views
Sonar mvn scanner fails on upload timeout (10 seconds) SonarQube Server / Community Build maven , scanner	1	1279	March 21, 2022
Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project Neptune: Fail to request SonarQube Server / Community Build	4	1064	June 9, 2021
Sonar Scanner Timeout SonarQube Server / Community Build	4	6105	October 23, 2023
Sonar scan failed with java.net.SocketTimeoutException SonarQube Server / Community Build	5	4461	May 14, 2020
Socket timeouts using maven sonar plugin SonarQube Server / Community Build sonarqube , maven	15	2981	June 29, 2021

Sonar Scanner Web Service Timeout still produces write timeout

Related topics