'why Curcible+FishEye fail to Index my SVN repository with a "connection timeout error: connect" when the test connection is working well?

I can add a repository and test the connection and I get the change set without any problem, but when come the indexing phase, it fail after 30 or 60 seconds with a connction timeout message.

Why?

4 answers

This widget could not be displayed.

Hello Jeannie,

Can you please try the suggestions given in the knowledge base article below:

https://confluence.atlassian.com/display/FISHKB/SVN+Operations+Taking+Longer+than+an+Hour+Time+Out

If this answer was helpful, please allow me to ask you to mark my answer as accepted in order to have it in the top of the thread, also helping other customers.

Thanks in advance!

Kind regards,
Felipe Kraemer

This widget could not be displayed.

Hello,

My problem is definitly not a timeout due to "longer than an hour time out". As I said in my post the timeout is a connection timeout and occure randomly within 30 to 100 seconds even if the connection test does not report any problem and the first phase that retrieve the change set works well.

 

Regards.

This widget could not be displayed.

Here is the Java error trace:

 

Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: connection refused by the server
svn: E175002: PROPFIND request failed on '...(removed for privacy)...'
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:106)
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:90)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:764)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359)
    at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710)
    at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doPropfind(DAVConnection.java:131)
    at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getProperties(DAVUtil.java:73)
    at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDir(DAVRepository.java:360)
    at org.tmatesoft.svn.core.io.SVNRepository.getDir(SVNRepository.java:1313)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.pushDirInfo(SvnRemoteGetInfo.java:183)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.pushDirInfo(SvnRemoteGetInfo.java:199)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.pushDirInfo(SvnRemoteGetInfo.java:199)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.pushDirInfo(SvnRemoteGetInfo.java:199)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.pushDirInfo(SvnRemoteGetInfo.java:199)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.pushDirInfo(SvnRemoteGetInfo.java:199)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:177)
    at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31)
    at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
    at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1258)
    at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
    at org.tmatesoft.svn.core.javahl17.SVNClientImpl.info2(SVNClientImpl.java:1671)
    ... 12 more
Caused by: java.net.ConnectException: Connection timed out: connect
    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
    at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
    at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    ... 3 more

This widget could not be displayed.

Command visible in the repository activity summary which is related to the indexing failure:

svn info -R -r 1000 http://SOME_URI@1000
Wed Mar 25 11:10:26 GMT+900 201527219ms

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

112 views 2 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you