FileMoveDetectionStep causing issues with older sonar analysis results?

[oer...@gmail.com]

Hi,

We recently upgraded from a fairly old (sorry I don't know the exact version) sonar version to 6.0.

On one of the projects I'm getting this error (obscured filenames):

java.lang.IllegalStateException: Original file OriginalFile{id=19253, key='FILE_A.JAVA'} already registered for file ComponentImpl{key='FILE_A_MOVED.JAVA ', type=FILE, uuid='AVcpQJHtCMovtXq-OKsy', name='', description='null', fileAttributes=FileAttributes{languageKey='java', unitTest=false}, reportAttributes=ReportAttributes{ref=34, version='null', path='FILE_A_MOVED.JAVA'}}. Unable to register OriginalFile{id=19252, uuid='72250b37-a88d-4b5d-9971-21f5136a2195', key='UNRELATED_FILE.JAVA'}.

at com.google.common.base.Preconditions.checkState(Preconditions.java:197) ~[guava-18.0.jar:na]

at org.sonar.server.computation.filemove.MutableMovedFilesRepositoryImpl.setOriginalFile(MutableMovedFilesRepositoryImpl.java:41) ~[sonar-server-6.0.jar:na]

at org.sonar.server.computation.filemove.FileMoveDetectionStep.registerMatches(FileMoveDetectionStep.java:144) ~[sonar-server-6.0.jar:na]

at org.sonar.server.computation.filemove.FileMoveDetectionStep.execute(FileMoveDetectionStep.java:139) ~[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]

I think https://jira.sonarsource.com/browse/SONAR-8011 might also be related.

Is there any workaround for this issue?

Thanks,

Ewout

[Simon Brandhof]

Hi Ewout,

Unfortunately you face https://jira.sonarsource.com/browse/SONAR-8013 that is fixed in version 6.1. The first release candidate of this version will be published on Friday.

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/245e87c9-265e-4527-aff9-fa2944672734%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof