Issue to connect FishEye to svn repositories

[Wayne Trzyna]

Hi,

I have upgraded FishEye from version 2.7.13 to version 3.0.0. Since then I'm not able to connect to my repositories. I'm receiving this error message:

Repository paused due to error com.cenqua.fisheye.rep.RepositoryClientException: org.tigris.subversion.javahl.ClientException: svn: E210002: There was a problem while connecting to lettuce.cs.colostate.edu:22 org.tigris.subversion.javahl.ClientException: svn: E210002: There was a problem while connecting to lettuce.cs.colostate.edu:22 org.tmatesoft.svn.core.SVNException: svn: E210002: There was a problem while connecting to lettuce.cs.colostate.edu:22 java.io.IOException: There was a problem while connecting to lettuce.cs.colostate.edu:22 java.io.IOException: Key exchange was not finished, connection is closed. java.io.IOException: The server hostkey was not accepted by the verifier callback. org.tmatesoft.svn.core.SVNAuthenticationException: svn: E215003: Host key ('lettuce.cs.colostate.edu:22 <ssh-rsa>') can not be verified.

[Gurleen Anand [Atlassian]]

Fisheye is bundled with the svnkit client and is the recommended svn client:

https://confluence.atlassian.com/display/FISHEYE/SVNkit+Client

Just removing the native svn client configuration from Fisheye's UI should be enough: https://confluence.atlassian.com/display/FISHEYE/Native+Subversion+Client without having to restart the application.

[CodeForCoffee]

Hi Wayne,

Did you figure something out? I'm fighting with the same issue, using 3.0.2. From https://jira.atlassian.com/browse/FE-4433 it doesn't look like a fix is coming until 3.1.0. At Nick what does removing the Native JavaHL SVN configuration entail?

[Nick]

Can you please try removing the Native JavaHL SVN configuration and restart FishEye.

The pure Java svn client (svnkit) should be adequate. https://confluence.atlassian.com/display/FISHEYE/SVNkit+Client

Otherwise, try the latest 3.0.2 version of FishEye. There was definitely a fix for JavaHL in there.

Cheers,

Nick