Philip, I should have stated we are using HTTP. I do not think we were using the neon library as we took the default install settings.
Based on that what you said where do you set the http-timeout? I have a consistent issue with the cli version of SVN where a full export of a code branch is timing out after 20-30 min. I have added http-timeout = 3600 to my local servers file but that has not made a difference. I don't think this is a server issue as I am not getting a peer reset message. I keep getting: svn: E175012: Connection timed out Thanks Tom On Thu, May 1, 2014 at 8:40 AM, Philip Martin <philip.mar...@wandisco.com> wrote: > Tom Kielty <calbuildmas...@gmail.com> writes: > > > A week ago I upgraded our server from 1.7.5 to 1.8.8. On an automated > build > > machine we had no issues with timeouts in 1.7.5. However, after upgrading > > to 1.8.8, client CLI as well, I am running into this time out error about > > 60% of the time. I have at least one other user running into this as > well. > > > > Any ideas or suggestions as to how to correct or work around this issue? > > If you were using a 1.7 client over HTTP with the default neon library > then the default HTTP timeout was 60min. The 1.8 client no longer > supports neon and uses serf instead and the default HTTP timeout is now > 10min. You can change the client timeout by changing the 'http-timeout' > setting in the client configuration. > > -- > Philip Martin | Subversion Committer > WANdisco // *Non-Stop Data* >
