Affects Version/s: None
Fix Version/s: 7.7
Starting from 7.7 SonarQube will no longer start on 32-bits systems.
The technical constraints is that Elasticsearch dropped support for such systems in 6.6. But functionally, it does not make sense to support this anymore and it chances are today super low that anyone is running a server application on a 32 bits system anyway.
32-bits system will still be supported by the scanners.
Binaries to start SonarQube on 32 bits linux systems will be removed.
For all other systems and when using `java -jar`, SonarQube startup should fail with an explicite message when running on 32-bits systems.
Requirements doc should be updated to mention SonarQube does not support 32-bits system on the server side but still does on the scanner side.
In the same fashion ES did, we should stop setting the -server flag on any JVM we start:
Related to the previous change that 32-bit is no longer supported, the default `jvm.options` file that ships with Elasticsearch no longer includes the
`-server` flag. Previously, the installation of the Windows service would filter the `-server` flag because it is not compatible with the service. Since the default `jvm.options` file no longer includes `-server`, the filtering of this flag was removed from the installation of the Windows service. This means that if you have a `jvm.options` file that includes this flag you will need to remove it.