There's a crude workaround – kill the "Timer-n" thread which holds the lock on org.tmatesoft.svn.core.internal.util.SVNHashMap. Might make Fisheye unstable, though.

Work to do here:

• get this deployed to eac/cru and atlaseye
• monitor the logs to see if the error recurs.

I had severe problems with this bug using http to scan the svn repositories. Fortunately I installed fisheye on the same server as the svn repositories so I could easily switch to the file protocol and that cured all problems. So if you want a fast fix using file instead of http might be it.
Note that having just one http repository will expose you to this bug.

Daily restarts aren't enough for us. We find we are restarted 2-3 times/day. We have 24x5 development and this is seriously impacting our ability to deliver. We really need this issue to be fixed. It has been outstanding for long enough! Any chance that it will be addressed in v2.8?

This error drives me crazy! Waiting for a fix!!!

We have the same problem on Fisheye 2.7.10 - but it seems to be quite random (once every 1 to 14 days).

After a restart it's working properly again.

A resolution would be very appreciated!!

I am having similar problems with SVN repos on FishEye 2.7.3. Every so often (once or twice a month), FishEye will start logging this message every minute:

2012-04-29 12:24:33,972 WARN  - Interrupting SVN operation thread due to non-response: IncrementalPinger1:86

When this starts occurring, it blocks ALL other repositories (git and svn alike) from getting updates. The only way I've found to redover is to restart FishEye, and even stopping FishEye (using the bin/stop.sh script) gets some failures:

2012-04-29 12:25:59,657 ERROR - Timed out waiting on 1 sessions to close, forcing shutdown
2012-04-29 12:26:34,005 WARN  - Interrupting SVN operation thread due to non-response: IncrementalPinger1:86
2012-04-29 12:26:37,954 WARN  - could not shutdown some repositories after 20 attempts

A daily restart, as suggested by the comments above, seems like the best workaround for now.

We are seeing this with Fisheye 2.7.6. Any update on resolution?

The Indexer locks up while "Indexing has commenced for repository <....>". The log states: [SvnTimeout ] fisheye.app com.cenqua.fisheye.svn.SvnThrottledClient-doInterrupt - Interrupting SVN operation thread due to non-response: IncrementalPinger1:78

We have to restart FishEye to get it working again. As Gael Neuez already opened a support issue, we won't open another one.. for now.

Hi, we recently hit this problem as well on our production environment; I found this issue after I created a support issue on fisheye. It seems there is no way out of this problem
We have ~200 svn projects in our fisheye, I won't spend my time editing svn timeout value for each of them...