SVN Initial Indexing Fails Reporting connection refused by the server
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
During an initial indexing the following error pattern is reported:
1
2
3
4
5
6
Repository paused due to error com.cenqua.fisheye.rep.DbException: Problem getting diff information for revXXXXX
com.cenqua.fisheye.svn.diff.SvnDiffException: Exception processing diff for revision XXXXX
com.cenqua.fisheye.rep.RepositoryClientException: org.tigris.subversion.javahl.ClientException:
svn: connection refused by the server org.tigris.subversion.javahl.ClientException:
svn: connection refused by the server org.tmatesoft.svn.core.SVNException:
svn: connection refused by the server java.net.ConnectException: Connection refusedThe problem usually happen when the SVN Server uses inetd/xinetd to service the svnserve protocol.
Cause
Fisheye is creating too many connections, disrupting other svnserve-based connections. This makes the Subversion Server refuse new connections.
Resolution
At the Subversion repository configuration in Fisheye, set option Throttle connections-per-sec so that the number of connections can be limited:
Go to the Fisheye Admin console, under "Repositories", open the Subversion repository configuration.
Under "SVN Details", section "SVN Options", set option "Throttle connections-per-sec" to 25.
Save the new configuration and Restart the repository so that the initial indexing can be resumed.
Was this helpful?