Subversion repository failing after migrating 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

Subversion repository not working after migrating Fisheye/Crucible to another server machine.

The following appears in the atlassian-fisheye-<date>.log:

1 2 3 4 5 6 7 2014-01-12 13:50:08,097 ERROR - SVN jar does not exist: /usr/share/java/svn-javahl.jar 2014-01-12 13:50:08,282 WARN - Could not load svn-javahl java.lang.NoClassDefFoundError: org/tigris/subversion/javahl/SVNClient at com.cenqua.fisheye.svn.util.SvnLoader.onLoaded(SvnLoader.java:48) at com.cenqua.fisheye.svn.util.SvnLoader.checkLoaded(SvnLoader.java:27) at com.cenqua.fisheye.svn.SvnScmConfig.init(SvnScmConfig.java:135) at com.cenqua.fisheye.config.ConfigUtil.initScmConfig(ConfigUtil.java:80)

Cause

svn-javahl.jar file is not installed in the migrated server machine.

Resolution

  1. Install and setup Native Subversion Client

  2. Restart Fisheye/Crucible

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.