title: Intermittent read timeout failures when analyzing java8 code with sonarqube 4.5.2
body: <p>I've been using sonarqube for a long time. More specifically I was using version 4.2 during the last months without any problems. Yesterday I updated sonarqube to its last version, 4.5.2, but now I'm facing intermittent failures when I issue a "mvn sonar:sonar" during my build process. That is, sometimes the whole build works as expected, but most of the attempts fail with errors like this:</p>
  
  <pre><code>build   10-Jan-2015 16:50:57    [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project project-parent: Unable to request: /batch/project?key=br.com.codersapiens:project-parent&amp;preview=false: Read timed out -&gt; [Help 1]
  </code></pre>
  
  <p>It seems that my CI server is not properly sized for the tools I use (basically, Bamboo and Sonarqube):</p>
  
  <pre><code>apps@ubuntu12:~# uptime 
   16:50:01 up 172 days, 19:22,  2 users,  load average: 2.55, 2.06, 1.56
  </code></pre>
  
  <p>This virtual machine has only one virtual processor:</p>
  
  <pre><code>apps@ubuntu12:~# cat /proc/cpuinfo | grep "model name"
  model name  : Intel Core Processor (Haswell)
  </code></pre>
  
  <p>Regardless the high load for this modest VM, the build used to finish properly, with complete sonar analysis, when I was using qube's version 4.2.</p>
  
  <p>Is this new version of sonarqube less tolerant to eventual delays caused by a busy host? Is there some way of setting this read timeout to bigger values? </p>