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
4,364,106
Community Members
 
Community Events
168
Community Groups

Fisheye - E175002 Error

Repository paused due to error com.cenqua.fisheye.config.ConfigException: Could not access http://pbgsvn1/svn/bsw/ : org.apache.subversion.javahl.ClientException: svn: E175002: connection refused by the server svn: E175002: PROPFIND request failed on '/svn/bsw' com.cenqua.fisheye.rep.RepositoryClientException: org.apache.subversion.javahl.ClientException: svn: E175002: connection refused by the server svn: E175002: PROPFIND request failed on '/svn/bsw' org.apache.subversion.javahl.ClientException: svn: E175002: connection refused by the server svn: E175002: PROPFIND request failed on '/svn/bsw' org.tmatesoft.svn.core.SVNException: svn: E175002: connection refused by the server svn: E175002: PROPFIND request failed on '/svn/bsw' java.net.ConnectException: Connection timed out: connect

Hi,

Index does not finish or gets extremly slow.
this error appears on big data svn. It took 1 week to index 48%. At at 48% the first errors like these appear.

fisheye is on Server 1 and svn on Server 2.
fisheye makes http request to svn and svn apache has 2 hours timeout.
fisheye timeout must be default 60minutes.
The last operation was 45minutes I saw. So it could be a timeout. When I do the svn commands on my computer they are 100 times faster.

So solution:
mirror svn to fisheye server and use file protocol?!

1 answer

Patchday was the reason.

 

Indexing is at 48.8% now. Extremely slow from Rev 90000 to 145000.
We are using http.
I now that file:// ist faster, but why is http sooo slow. Over one week already. Maybe the cache, spooling or other settings in the VM Win64?

Hi,

Even I face the same issues, the index is too slow for one of my repository and cant find a way to fix it, how did you fix this issue?

-Syed KM

Hi Syed,

finally it finished, but if not, we would make a clone / mirror on the same location like jira / fisheye installation and then do the fisheye indexing via ftp and not via http. Must be way faster.

Suggest an answer

Log in or Sign up to answer