Builds failing in Bamboo with connection error from SVN server svn: E175002 error.

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptom

When attempting to connect to a SVN server Bamboo build faces  connection issues  while executing the process configured . The build fails with  svn: E175002: Connection reset error.

Error in build logs
build   30-Jun-2022 07:40:33    [INFO] BUILD FAILURE
build   30-Jun-2022 07:40:33    [INFO] ------------------------------------------------------------------------
build   30-Jun-2022 07:40:33    [INFO] Total time: 09:29 h
build   30-Jun-2022 07:40:33    [INFO] Finished at: 2022-06-30T07:40:33+00:00
build   30-Jun-2022 07:40:34    [INFO] Final Memory: 870M/18189M
build   30-Jun-2022 07:40:34    [INFO] ------------------------------------------------------------------------
build   30-Jun-2022 07:40:34    [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sona
r (default-cli) on project v3-product: Error when executing blame for file benefits/src/com/vitechinc/v3/enrollment/services/En
rollmentServiceImpl.java: svn: E175002: Connection reset
build   30-Jun-2022 07:40:34    [ERROR] svn: E175002: REPORT request failed on '/repos/!svn/bc/1792132/v3-web-product/branches/
v310-uc/benefits/src/com/vitechinc/v3/enrollment/services/EnrollmentServiceImpl.java'


Cause

This connection error occurs because the request processing is taking a long time and the SVN server is closing the connection.


HTTP spooling helps to prevent issues with request processing taking a long time and the server closing the connection.

Resolution


An option was added to SVNKit 1.8.8 to address this:

Adding an option to enable HTTP spooling in SVNKit will fix this issue.


Add the -Dsvnkit.http.spoolDirectory=<path_to_a_temporary_folder> in the MAVEN_OPTS.



Last modified on Aug 1, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.