Sonar 3.6.1 Unable to request: /batch_bootstrap/properties

Question

We have Jenkins 1.509.2 + Sonar 3.6.1. And receive the below error, We didn't have the same error with Sonar 3.4.1 from which we upgraded. Could you advise how can we fix the issue?

Exception in thread "main" org.sonar.runner.RunnerException: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
 at org.sonar.runner.Runner.delegateExecution(Runner.java:288)
 at org.sonar.runner.Runner.execute(Runner.java:151)
 at org.sonar.runner.Main.execute(Main.java:84)
 at org.sonar.runner.Main.main(Main.java:56)
Caused by: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
 at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:82)
 at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:72)
 at org.sonar.batch.bootstrap.BatchSettings.downloadSettings(BatchSettings.java:96)
Caused by: java.net.SocketTimeoutException: Read timed out
 at java.net.SocketInputStream.socketRead0(Native Method)
 at java.net.SocketInputStream.read(SocketInputStream.java:150)
 at java.net.SocketInputStream.read(SocketInputStream.java:121)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:334)

The error is not received every time - more like 90%. After I have upgraded all the Installed plugins, the error disappeared, on the next day - it appeared again. It appears for ALL the projects, small and big. The Jenkins server is far (network wise) - from the Sonar server on most of the projects, but we also have projects that are in the same location with Sonar - and still receive this issue. Is there a workaround at least to increase the timeout?

Answer 1

We are seeing a similar error after upgrading from 3.4.1 to 3.6. The problem is not as severe as your (maybe 30% rather than 90%). Like your experience it is not limited to one project (errors in 2 out of every 7 builds). Restarting Sonar seems to help but does not always make it go away. Also, call me crazy but adding a -X flag to the maven build command has so far been the most reliable workaround. FYI, our builds are running on the same machine as the Sonar server (and the MySQL server).