6.0 - ERROR - Failed to execute task - NullPointerException: path can not be null

[in...@woutie.be]

I recently upgraded from sonar version 3.5.1 to 6.0. The automatic upgrade of the different LTS version in between went very smooth.

The new maven sonar plugin does it's work and sends all data to the sonarqube server. But on the server the analysis task fails. See stacktrace below.

Any idea of a workaround, or should we just use the latest LTS? How stable is the 6.0 release?

2016.08.19 12:26:27 ERROR [o.s.s.c.t.CeWorkerCallableImpl] Failed to execute task AVaiVjwGUTGVFczyzwQX
java.lang.NullPointerException: path can not be null
	at java.util.Objects.requireNonNull(Objects.java:228) ~[na:1.8.0_91]
	at org.sonar.server.computation.filemove.FileSimilarity$File.<init>(FileSimilarity.java:36) ~[sonar-server-6.0.jar:na]
	at org.sonar.server.computation.filemove.FileMoveDetectionStep.getFile(FileMoveDetectionStep.java:236) ~[sonar-server-6.0.jar:na]
	at org.sonar.server.computation.filemove.FileMoveDetectionStep.computeScoreMatrix(FileMoveDetectionStep.java:208) ~[sonar-server-6.0.jar:na]
	at org.sonar.server.computation.filemove.FileMoveDetectionStep.execute(FileMoveDetectionStep.java:126) ~[sonar-server-6.0.jar:na]
	at org.sonar.server.computation.step.ComputationStepExecutor.executeSteps(ComputationStepExecutor.java:64) ~[sonar-server-6.0.jar:na]
	at org.sonar.server.computation.step.ComputationStepExecutor.execute(ComputationStepExecutor.java:52) ~[sonar-server-6.0.jar:na]
	at org.sonar.server.computation.taskprocessor.report.ReportTaskProcessor.process(ReportTaskProcessor.java:75) ~[sonar-server-6.0.jar:na]
	at org.sonar.server.computation.taskprocessor.CeWorkerCallableImpl.executeTask(CeWorkerCallableImpl.java:81) [sonar-server-6.0.jar:na]
	at org.sonar.server.computation.taskprocessor.CeWorkerCallableImpl.call(CeWorkerCallableImpl.java:56) [sonar-server-6.0.jar:na]
	at org.sonar.server.computation.taskprocessor.CeWorkerCallableImpl.call(CeWorkerCallableImpl.java:35) [sonar-server-6.0.jar:na]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_91]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_91]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_91]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_91]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_91]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_91]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_91]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
2016.08.19 12:26:27 ERROR [o.s.s.c.t.CeWorkerCallableImpl] Executed task | project=com.trax:platform-payments | type=REPORT | id=AVaiVjwGUTGVFczyzwQX | time=10027ms

[Julien Lancelot]

Hi,

From the stacktrace, I can see that this issue is coming from the file move feature, introduced in 6.0. 

You need to revert to 5.6.X, then relaunch every analysis, then migrate to 6.0.

Regards,

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/dad909bb-fe54-49b3-938e-41c06e85cb51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Julien LANCELOT | SonarSource

http://sonarsource.com

[Simon Brandhof]

As Julien said, analysing your projects with version 5.6 should fix the issue when upgrading to 6.0. 

However the bug will be fixed in 6.1 : https://jira.sonarsource.com/browse/SONAR-8011.

Regards