Indexing Fails Reporting "Error: Attempt to load isDeleted from non existent revid = -1"

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 the initial indexing process of an SVN repository the following error is reported causing the indexing to stop:

1 2 3 4 5 6 7 8 9 10 11 ERROR [InitialPinger1 Repo_Name] fisheye.app DiffChangeSetProcessor-processFileRevisions - Unable to process change path "/folder1/tags/7.0.0.1078" in revision 22749 com.cenqua.fisheye.rep.DbException: Attempt to load isDeleted from non existent revid = -1 at com.cenqua.fisheye.rep.impl.CommonRevInfoDAO.isDeleted(CommonRevInfoDAO.java:1688) at com.cenqua.fisheye.svn.db.SvnRevInfoDAO.isDeleted(SvnRevInfoDAO.java:629) at com.cenqua.fisheye.svn.DiffChangeSetProcessor.updateTagRoot(DiffChangeSetProcessor.java:926) at com.cenqua.fisheye.svn.DiffChangeSetProcessor.applyTag(DiffChangeSetProcessor.java:874) at com.cenqua.fisheye.svn.DiffChangeSetProcessor.access$1000(DiffChangeSetProcessor.java:65) at com.cenqua.fisheye.svn.DiffChangeSetProcessor$4.visit(DiffChangeSetProcessor.java:842) at com.cenqua.fisheye.svn.db.SvnRevInfoDAO$1.visit(SvnRevInfoDAO.java:532) at com.cenqua.fisheye.rep.impl.CommonRevInfoDAO.visitPathInTree(CommonRevInfoDAO.java:1987) at com.cenqua.fisheye.rep.impl.CommonRevInfoDAO.visitDirectoryTree(CommonRevInfoDAO.java:1975)

Cause

The revision being indexed refers to a branch or tag created using "svn copy" and Fisheye is not able to find in the repository the revision or path of the svn copysource.

Fisheye 2.7.13 and newer versions will not experience this problem. In these versions, if the source can't be found, the revision will be indexed as a "svn add".

The issue may happen if the repository was corrupted (causing the information of the "svn copy" source to be lost) or if the source was excluded on purpose from Fisheye.

Resolution

The problem can be avoided if the path containing the branch or tag copied is Excluded from Fisheye. However, this may demand extensive work if there are multiple occurrences of the issue in the same repository. The best resolution for this problem is an upgrade to Fisheye 2.7.13 or newer versions.

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.