Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

'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

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

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

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.

0 votes

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

Suggest an answer

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

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their  Jira Cloud instance.  ...

481 views 16 17
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you