Read timed out on SonarQube analysis

Question

We previously discussed the problem on the now closed SonarQube Users mailing list.

The problem was solved by exchanging the for about half a week by optimizing the

Answer 1

The problem can be solved in 4 ways:

1. add more resources to SonarQube server process and/or server platform (e.g. faster disks)
2. upgrade SonarQube server to the newest version (e.g. a lot of performance problems have been fixed in SonarQube 5.2 - see release notes)
3. change timeout value in sources and compile custom server
4. add indexes on columns in database (not recommended, you can read executed SQL commands from logs in debug mode)