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
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
... 23 more
2013-10-04 02:26:16,692 ERROR [InitialPinger3 Varuna-test] fisheye RepositoryEngine-startPause - Repository scanner paused.
Thanks in advance.
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!
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?
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....
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!
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