Launch of SonarQube Server 4.5.6, tested with Maven 3.0.5, Maven 3.3.9,
Using the command line as follows:
mvn -B org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar
Also tested various versions of the plugin (3.1.1, etc.).
I already tested to improve memory settings from 2 G to 22 G
-Xmx6g -XX:-UseGCOverheadLimit
that didn't help. Verification always does not continue and receives this conclusion:
00:23:08.815 15:36:06.724 WARN - [JOURNAL_FLUSHER] WARNING Journal flush operation took 14.164ms last 8 cycles average is 1.770ms
00:23:55.507 15:37:10.917 WARN - [JOURNAL_FLUSHER] WARNING Journal flush operation took 3.696ms last 8 cycles average is 2.232ms
00:25:03.219 15:38:16.429 WARN - [JOURNAL_FLUSHER] WARNING Journal flush operation took 3.493ms last 8 cycles average is 898ms
00:29:09.760 15:42:01.239 WARN - [JOURNAL_FLUSHER] WARNING Journal flush operation took 3.513ms last 8 cycles average is 439ms
00:31:01.208 15:44:17.868 WARN - [JOURNAL_FLUSHER] WARNING Journal flush operation took 3.611ms last 8 cycles average is 451ms
00:34:22.694 15:47:30.643 WARN - [JOURNAL_FLUSHER] WARNING Journal flush operation took 22.496ms last 8 cycles average is 2.812ms
We have a large number of modules (about 600) in one assembly of several modules (Java / Tycho) ...
Update: therefore, the result remains unsuccessful. Does scanning really take up so much memory that the module executes modulo?
source
share