maven – SonarQube分析警告日志刷新操作(不结束)

2019年7月28日 409次阅读

运行SonarQube Server 4.5.6,使用Maven 3.0.5测试,Maven 3.3.9,

使用这样的命令行：

mvn -B org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar

还测试了不同版本的插件(3.1.1等).

我已经测试过将内存选项从2 G增加到22 G

-Xmx6g -XX:-UseGCOverheadLimit

这没有帮助.始终扫描不会继续并获得此输出：

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

我们在单个多模块构建(Java / Tycho)中有大量模块(大约600个)……

更新：结果保持失败.扫描是否真的需要一个模块完成的内存？

最佳答案 经过更多的调查和研究,我发现了以下相关问题：

> https://jira.sonarsource.com/browse/SONAR-5995
> https://jira.sonarsource.com/browse/SONAR-5878
> https://jira.sonarsource.com/browse/SONAR-5551

换句话说,我必须将SonarQube版本更新为更新版本.

点赞