After upgrading to 3.1, Fisheye is hanging (with no errors in the log) when re-indexing our existing SVN repo:
We found that our indexing operation was hitting the default subversion timeout in fisheye. Single changesets were taking more than an hour to complete (timing out at an hour). This was confirmed by the indexing log (in the UI) showing one operation taking >3600000ms. We increased the timeout to a few hours and got through the repo (slowly).
Unfortunately we didn't find a solution. It still happens sometimes with the most recent version and the most recent java versions but not very frequently and only with the file:// protocol. As workaround I temporary switch to the http:// protocol until the indexing is past the problematic revision and then back to the file protocol for the extra speed.
I increased the timeout two 2 hours, but now I see the following error every 2 hours (instead of every hour):
2014-04-08 16:28:38,063 ERROR - Problem processing revisions from repo public due to class com.cenqua.fisheye.rep.RepositoryClientException - java.util.concurrent.TimeoutException
We setup our fisheye instance to use a local mirror of our subversion tree from disk with "file:///var/svn-repo". So I'm not sure if increasing the timeout will actually help. It might be some svn locking issue.
For now I've set the timeout to 20 hours and hopefully it will finally process the specific commit (which isn't anything much bigger than normal).
I'll report back when I've more info.
Some more info on our system:
# cat format 5 # cat db/format 6 layout sharded 1000
# svn --version
svn, version 1.8.5 (r1542147) compiled Feb 13 2014, 00:11:36 on x86_64-unknown-linux-gnu
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot