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

svn checkout fails on large projects with large files

Trying to check out a large project with several large files usually fails with the error message.

svn: REPORT of '/svn/!svn/vcc/default': Could not read response body: Secure connection truncated

Web searches seem to indicate that this is a server side issue.

Are there things to do on my end to prevent this?

5 answers

1 accepted

2 votes
Answer accepted

Atlassian have informed us (via another ticket) that due to a 15 minute hard timeout on the ngnix web server that sits in front of Fisheye SVN in OnDemand, checkouts with large files may never complete. This timeout is enforced even if the connection is submitting data (it's not an idle timeout)

OnDemand is different to JIRA Studio hosted in this respect, which didn't utilise Ngnix, so checkouts under JIRA Studio for the same repos wouldn't be affected in this way. I'm amazed no-one from Atlassian has been along and answered this one for you.


Hy i've got the same problem , i used TortoiseSVN and RapidSVN  still:

Error while performing action:REPORT of '/..../.../!svn/me' could not read response body: An existing connection was forcibly closed by the remote host.

We are experiencing the problem right now trying to download a large project. The download ran for about 40 minutes and then stopped with the following.

svn: E175002: SSL peer shut down incorrectly

svn: E175002: REPORT request failed on '/svn/!svn/vcc/default'

is there any work around for this? I am working on a migration plan but don't expect to begin implementation until this summer.

I'm seeing this right now on a large checkout from our repo on a jira studio instance.

I'm going to migrate our source to the server soon and am configuring Hudson to test builds but checkouts are failing with


SVNException: svn: SSL peer shut down incorrectly

svn: REPORT request failed on '/svn/!svn/vcc/default'

and an svn checkout on the command line of my own machine failed with

Secure connection truncated

After a brief downtime, atlassians servers are back up, and the problems seems to be gone.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

316 views 0 10
Join discussion

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