SVN Integration Stops Working Interrupting SVN operation thread
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Symptoms
Fisheye stops indexing some repositories and in the logs the following message can be seen:
1
2013-02-07 16:17:46,615 INFO [SvnTimeout ] fisheye.app SvnThrottledClient-doInterrupt - Interrupting SVN Operation thread on repository 'ACME' due to non-response: IncrementalPinger1:91Cause
Fisheye is calling an operation against the SVN Server and the server does not respond back within the timeout period. After timing out, Fisheye sends a cancel request and waits for the SVN Server to confirm that the operation has been canceled, without any response from the SVN Server.
Workaround
The following workarounds can be applied:
Use svnsync to mirror the repository onto the same server where Fisheye is located and then use the
file://protocol to access the repository instead ofhttp://protocol. Please refer to Tuning Fisheye performance for more information.Switch to the Native Subversion Client, which is known to better handle SVN cancel operations.
In addition to doing either of the above options, the Svn Operation Timeout setting in the Fisheye repository Administration > Repository Settings > Repositories > <Repository Name> can be increased to a value between 3 to 24 hours.
Resolution
Upgrade Fisheye/Crucible 2.9.0+ since it has restructured the SVN operations FE-1071 - Restructure FishEye so that svn operations do not occur on the main thread
Was this helpful?