Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

fisheye evaluation

We are presently evaluating FISHEYE + CRUCIBLE for our review and repository integration purposes. The SCM in use is SVN. Whenever any new repository is defined in Fisheye, the initial indexing throws up the following error: -

Repository paused due to error com.cenqua.fisheye.rep.RepositoryClientException: org.apache.subversion.javahl.ClientException:svn: E210004: Handshake failed, received:" org.apache.subversion.javahl.ClientException:svn: E210004: Handshake failed, received:" org.tmatesoft.svn.core.SVNException: svn: E210004: Handshake failed, received:"

Why is this error occuring so many times?

This error is thrown at times even for repositories that have finished the initial scanning and indexing processes.

Please help resolve this ASAP

3 answers

I have increased the allocated disk space for the application's data folder. At that time, it was showing a lack of disk space because the Fisheye "backup" was eating up all the disk space. Now that has been sorted out. Still, the indexing process is not working properly.

Here is how I have configured the repositories in FISHEYE: -

The SVN server: version 1.3

SVN client: the bundled svnkit 1.7.x

The SVN repository has been broken down into several FISHEYE repositories, each one has been optimized so as to include only the necessary source folders and exclude all other types of folders. Even within the "source", i have included only those versions that are actually under maintenance or development.

The indexing process shows several repositories in "running" status. However, when we open the files to view the source or diff, then many files show the error: "unable to fetch content". Also, many files do not show "Full content" once they are added to a review. Only the diff information is available, full content is not available. No error is shown in this case, the application simply ignores the request for full content.

Why is the indexing process not happening thoroughly for all files and folders?

Do I need to specify any rules concerning the folder format?

Do the svnkit and the SVN server versions (mentioned above) work well with each other or are there any known issues that we have failed to notice?

Do I need to upgrade the FISHEYE instance for better performance?

Can there be some "socket" level problem that is affecting us?

Please help us resolve this, because we are on the verge of actually buying this product for our development center.

The problem seems to be with the indexing happening over a network connection and also due to shortage of disk space. We are presently working on mirroring the SVN repository and also increasing the space allocation. Hopeful that these steps should resolve the issue.

0 votes

Hi Sangeeta,

I'm afraid it is not clear from the error message what is the cause of that, would you consider raising support request so we could look into the details? Please include more details is possible:

  1. full stack trace of the error from log file
  2. is the problem intermittent or permanent?
  3. which protocol do you use to connect to your SCM? Local file:/// protocol, svn or rather http(s)?
  4. what version of svn is used on the SCM side

Kind regards,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

172 views 1 6
Read article

Atlassian Community Events