Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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 3.1 stuck at 99% indexing and will not finish

After upgrading to 3.1, Fisheye is hanging (with no errors in the log) when re-indexing our existing SVN repo:

<label class="GBRQCM4CCC"> Current Activity:</label>Full indexing in-progress<label class="GBRQCM4CCC"></label>
<label class="GBRQCM4CCC"> Status Message:</label>Expanding paths of changeset 3559
It says its99.9% complete.. but will not finish. New committs are not shown. If I restart fisheye, the last commit will then appear and it then gets stuck again at the same point.

9 answers

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).

HI @TomB,

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.


Thanks. I may try your http workaround as well since increasing the timeout doesn't seem to help.

To @Hippo CMS Infra Team, have you had success tracking down the cause of the indexing timeout?  We're attempting to reindex a local copy of a single repo and it's been stuck at 77% for two weeks now while expanding paths of changesets.


Now I get I timout after 20 hours :-( I'll raise an issue with atlassian.

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:

Fisheye 3.3.3

java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) Server VM (build 24.51-b03, mixed mode)
SVN repo:

# cat format
# cat db/format 
layout sharded 1000

# svn --version

svn, version 1.8.5 (r1542147) compiled Feb 13 2014, 00:11:36 on x86_64-unknown-linux-gnu

Thanks! I'll try that.

Any progress on this issue? We're having the same issue..

0 votes
francis Marketplace Partner Dec 02, 2013

Same here, will file a support issue

We're seeing similar behavior. Fisheye 3.1.4. Hanging expanding the same changeset.

Suggest an answer

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

🎨 Add some visual life to your templates

Hi Atlassian Community, My name is Avni Barman, and I am a Product Manager on the Confluence Cloud team. Based on feedback from you, we are giving admins more power to create templates that a...

224 views 4 9
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