Error when executing blame for file **/src/com/**/**/**/Filename.java - Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: Connection reset

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using - Sonarqube Community Edition Version 8.4.1 (build 35646) , sonar-maven-plugin3.7 , [Jenkins 2.235.5] with SVNKIT 1.10.1
  • what are you trying to achieve - clean package sonar:sonar -DsonarServerURL=sonarServerIP:9000
  • what have you tried so far to achieve this. Scan successful with <sonar.scm.disabled>true</sonar.scm.disabled> and result published to SonarQube

When <sonar.scm.disabled>false</sonar.scm.disabled> the sonar scan fails with Error when executing blame for file : svn: E175002: Connection reset

This happens for one file with 32000 lines of code, but the same is working file with Sonar sonar-maven-plugin 3.2

Error trace:

[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] **10792**/16890 source files have been analyzed
.
.
Repeated 150 times 
.
.
...
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project aaspire-app: Error when executing blame for file <filename>: svn: E175002: Connection reset
[ERROR] svn: E175002: REPORT request failed on '<filename>'
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project aaspire-app: Error when executing blame for file <filename>
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

Caused by: org.apache.maven.plugin.MojoExecutionException: Error when executing blame for file <filename>
    at org.sonarsource.scanner.maven.bootstrap.ScannerBootstrapper.execute (ScannerBootstrapper.java:67)
    at org.sonarsource.scanner.maven.SonarQubeMojo.execute (SonarQubeMojo.java:104)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.jvnet.hudson.maven3.launcher.Maven35Launcher.main (Maven35Launcher.java:130)
 
Caused by: java.lang.IllegalStateException: Error when executing blame for file <filename>
    at org.sonar.plugins.scm.svn.SvnBlameCommand.blame (SvnBlameCommand.java:85)
    at org.sonar.plugins.scm.svn.SvnBlameCommand.blame (SvnBlameCommand.java:58)
    at org.sonar.scanner.scm.ScmPublisher.publish (ScmPublisher.java:84)
    at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart (ProjectScanContainer.java:358)
    at org.sonar.core.platform.ComponentContainer.startComponents (ComponentContainer.java:137)
    at org.sonar.core.platform.ComponentContainer.execute (ComponentContainer.java:123)
    at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart (GlobalContainer.java:144)
    at org.sonar.core.platform.ComponentContainer.startComponents (ComponentContainer.java:137)
    at org.sonar.core.platform.ComponentContainer.execute (ComponentContainer.java:123)
    at org.sonar.batch.bootstrapper.Batch.doExecute (Batch.java:72)
    at org.sonar.batch.bootstrapper.Batch.execute (Batch.java:66)
    at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute (BatchIsolatedLauncher.java:46)

Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: Connection reset
svn: E175002: REPORT request failed on '/svn//!svn/bc/151168/branches/<Finename>'
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error (SVNErrorManager.java:112)
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error (SVNErrorManager.java:96)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request (HTTPConnection.java:765)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request (HTTPConnection.java:352)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request (HTTPConnection.java:340)
    at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest (DAVConnection.java:910)
    at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport (DAVConnection.java:363)
    at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport (DAVConnection.java:353)
    at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getFileRevisionsImpl (DAVRepository.java:936)
    at org.tmatesoft.svn.core.io.SVNRepository.getFileRevisions (SVNRepository.java:763)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteAnnotate.run (SvnRemoteAnnotate.java:109)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteAnnotate.run (SvnRemoteAnnotate.java:30)
    at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run (SvnOperationRunner.java:21)
    at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run (SvnOperationFactory.java:1239)
    at org.tmatesoft.svn.core.wc2.SvnOperation.run (SvnOperation.java:294)
    at org.tmatesoft.svn.core.wc.SVNLogClient.doAnnotate (SVNLogClient.java:295)
    at org.sonar.plugins.scm.svn.SvnBlameCommand.blame (SvnBlameCommand.java:83)
    at org.sonar.plugins.scm.svn.SvnBlameCommand.blame (SvnBlameCommand.java:58)
    at org.sonar.scanner.scm.ScmPublisher.publish (ScmPublisher.java:84)
    at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart (ProjectScanContainer.java:358)
    at org.sonar.core.platform.ComponentContainer.startComponents (ComponentContainer.java:137)
    at org.sonar.core.platform.ComponentContainer.execute (ComponentContainer.java:123)
    at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart (GlobalContainer.java:144)
    at org.sonar.core.platform.ComponentContainer.startComponents (ComponentContainer.java:137)
    at org.sonar.core.platform.ComponentContainer.execute (ComponentContainer.java:123)
    at org.sonar.batch.bootstrapper.Batch.doExecute (Batch.java:72)
    at org.sonar.batch.bootstrapper.Batch.execute (Batch.java:66)
    at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute (BatchIsolatedLauncher.java:46)

error.txt (6.6 KB)

Is there way to increase timeout or any alternate option? I have already tried -Dhudson.spool-svn=true still same error is thrown.

Am not sure why this is working fine in SonarQube Version 6.7 (build 33306) and sonar-maven-plugin - 3.2

Please assist, let me know in case more details is required

3

Hello,
It’s strange that a different version of the sonar-maven-plugin would have any effect on it, since the scanner that runs is downloaded from the SonarQube server. Are you sure it’s not a different version of SonarQube that changes the outcome?

4

Or maybe it’s unstable and it sometimes fails even with the same versions?
It looks like the cause of the error is a network problem between the SVN client and the SVN server.

5

Hi @dmeneses,

Thanks for taking time looking into to post. You are correct, the scan works fine with SonarQube Version 6.7 (build 33306) with Sonar-maven-plugin v3.2.

Same set up is failing for SonarQube Version 8.4.1 (build 35646) with Sonar-maven-plugin v3.7.

The issue could be in SonarQube Version 8.4.1. Looking at the log scanner is able to scan most of the files but gets stuck on one file (number 10792) and fails with the error attached in the post.

[INFO] 10744/16890 source files have been analyzed
[INFO] 10754/16890 source files have been analyzed
[INFO] 10763/16890 source files have been analyzed
[INFO] 10774/16890 source files have been analyzed
[INFO] 10783/16890 source files have been analyzed
[INFO] 10791/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed
[INFO] 10792/16890 source files have been analyzed

The error starts from
at org.sonar.plugins.scm.svn.SvnBlameCommand.blame (SvnBlameCommand.java:83)
at org.sonar.plugins.scm.svn.SvnBlameCommand.blame (SvnBlameCommand.java:58)
at org.sonar.scanner.scm.ScmPublisher.publish (ScmPublisher.java:84)

The blame fails only for this file, other files prior to encountering the offending file is working fine.

I tried to get the blame via PS and its works fine, takes around 1min 30sec

blame-PS
blame-PS840×211 72.8 KB

Hope this information helps, please let me know if there is anything I can try.

6

Hi @dmeneses,

I tried multiple times and it fails in the same step getting the blame information and always for the same offending file. Did not face this issue in SonarQube 6.7

Is there timeout set by sonarqube when get blame is invoked?

7

No. Based on the error message, it looks like the network connection is lost. If it only happens on the large file, maybe it’s because the operation takes too long.

The fact that the native svn client works makes me think it’s a problem with SVNKit, which is the java svn library used by the SonarQube scanner, unless it can be configured differently by the scanner to resolve the problem. SonarQube is already using the latest version of SVNKit so there isn’t an update we can try out.

SVNKit’s bug tracker is down so I can’t see if a related bug has been reported.
From here, I think the next step would be for you to try to get debug logs out of SVNKit, to see if any more details about the error are given.

8

Thanks for the update @dmeneses. As suggested will try to get the debug log from SVNKit and request for review from tmatesoft support.

Regards
K

9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.