Restructure SVN repository and get Fisheye index with it


We have an unconventional svn repository structure. With the current repository structure, it is not possible to define symbolic rules in Fisheye. Therfore, I decided to restructure the repository to have a more conventional structure so that Fisheye does not have complains regarding that. However, after restructuring and initiating the Fisheye indexing, I get the following error

Problem processing revisions from repo Varuna-test due to class com.cenqua.fisheye.rep.RepositoryClientException - java.util.concurrent.TimeoutException

com.cenqua.fisheye.rep.RepositoryClientException: java.util.concurrent.TimeoutException

at com.cenqua.fisheye.svn.SvnThrottledClient.executeNoThrottle(

at com.cenqua.fisheye.svn.SvnThrottledClient.execute(

at com.cenqua.fisheye.svn.SvnThrottledClient.info2(

at com.atlassian.fisheye.svn.Svn2Infill2Processor.getInfo(

at com.atlassian.fisheye.svn.Svn2Infill2Processor.infillChangeSet(

at com.atlassian.fisheye.svn.Svn2Infill2Processor.access$100(

at com.atlassian.fisheye.svn.Svn2Infill2Processor$1.perform(

at com.atlassian.fisheye.svn.Svn2Infill2Processor$1.perform(

at com.cenqua.fisheye.cache.BaseRevisionCache.withDbWriteLock(

at com.atlassian.fisheye.svn.Svn2Infill2Processor.process(

at com.atlassian.fisheye.svn.Svn2Scanner.slurpRepository(

at com.atlassian.fisheye.svn.Svn2Scanner.doSlurpTransaction(


at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(

at com.cenqua.fisheye.rep.RepositoryEngine.slurp(




at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(

at com.cenqua.fisheye.rep.RepositoryHandle.access$100(

at com.cenqua.fisheye.rep.RepositoryHandle$

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$ Source)

at Source)

Caused by: java.util.concurrent.TimeoutException

at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)

at java.util.concurrent.FutureTask.get(Unknown Source)

at com.cenqua.fisheye.svn.SvnThrottledClient.executeNoThrottle(

... 23 more

2013-10-04 02:26:16,692 ERROR [InitialPinger3 Varuna-test] fisheye RepositoryEngine-startPause - Repository scanner paused.

My target is to keep the past revisions in the same repository and restructure the repository so that it follows a conventional structure. I have defined the symbolic rules as well in order to support the new structure. It works well and indexes properly if I create a new such repository structure from scratch. But, it fails to index if I restructure the old repository to match the new structure. In the process, I am renaming trunk and branches folder. Does it have to do anything with the failure in indexing?

Thanks in advance.


2 answers

0 votes

Hello Kaustav,

It looks like it's just timing out while indexing your repository. The default timeout is '1 hour'. Can you try to set/increase the Svn Operation Timeout to a higher value? Maybe you can try to use '6 hours'.

Also, if you don't mind about the old repository structure, you can configure FishEye to index your repository from the revision where you committed the new repository structure onwards, by configuring a Start Revision.

I hope this helps!

Helle Felipe,

Thank you for the response. I tried by putting in the starting revision as the last (head) revision of svn. However, I did not add any customized timeout before. With this configuration, I tried to have the repository indexed. However, it did not proceed beyond 0% scanning. This time I have added the timeout option. So far, it is showing the same i.e. 0% scanning. I do not think it should take so long to index as well. Is there some other config changes that I can tweak?

Hi Tini,

Thank you for the details. I was able to get it working by increasing the "svn operations timeout" for now. I was unable to get this workaround working.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

56 views 1 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you