Version of Sonar Scanner used: org.sonarsource.scanner.maven:sonar-maven-plugin:126.96.36.1996: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:188.8.131.526: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]
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.
I could imagine the problem is that sonar.ws.timeout is only used for read timeout
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.