Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Fisheye com.cenqua.fisheye.rep.RepositoryClientException

Repository paused due to error com.cenqua.fisheye.rep.RepositoryClientException: java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E150000: 'https://svnurl/trunk' does not exist in revision 6,764 java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E150000: 'https://svnurl/trunk' does not exist in revision 6,764 org.apache.subversion.javahl.Cli

1 answer

0 votes
Themis Atlassian Team Apr 11, 2018

Hi there,

The article  Errors When Trying to Add or Index a Repository - non-existent in revision may be relevant in your case! It offers three potential causes with their respective solutions.

We hope one of them will work for you!

Best,

Themis

@Themis I solved the above problem by changing SVN URL from https://rootpath/projectname/trunk to https://rootpath/ and adding projectname in the path.

 

Now i am facing another issue. The indexing process is taking a lot of time, it started indexing yesterday (April 10,2018) at 11:00 PM UTC and only indexed 5.7% as of (April 11 ,2018 10:00 PM UTC). Please let me know.

Themis Atlassian Team Apr 12, 2018

Hi,

glad that the initial problem is solved!

As for long indexing times, it is not unexpected that the initial scan and indexing of a repository takes a long time, depending on the size of the repo, and the size of the changesets. 

Having said that,  it seems you are using the https protocol, which is slower compared to svn: or file: You can consider mirroring your repository locally to be able to access it with the file:// protocol. You can find more information here to improve the Fisheye scan performance.

Also, here are a few more resources that may help you troubleshoot slow svn indexing:

Hope this helps!

Best,

Themis

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

98 views 2 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you