Hello Darly, What we could see from the error is that connection is closed by the server unexpectedly for the client. Common reason for that is (relatively) slow processing of the response on the client side which may cause output buffer being overflowed on the server side for a timeout time. There are of course might be other reasons for connection being closed unexpectedly in your particular environment.
I'm not aware of the load balancer algorithms, but might it be that it doesn't behave well in case of a huge http response being received by the client? Is there a way to bypass load balancer for checkout? BTW, I recall that another common reason for a similar problem is apache traffic rate limiting module, that might be configured to allow HTTP requests being processed only at certain maximum rate (assuming human browsing, not a software http client, like in Subversion case). Disabling such a module could also resolve the problem. Alexander Kitaev, TMate Software, http://subgit.com/ - Svn to Git Migration! http://svnkit.com/ - Java [Sub]Versioning Library! http://hg4j.com/ - Java Mercurial Library! http://sqljet.com/ - Java SQLite Library! On 29 May 2014 20:59, Darly Senecal Baptiste <dsenec...@gmail.com> wrote: > In my case the svn server is running behind of a f5 Load Balancer (SSL > Offolader). And what I understood from the the Network Engineer, that the > connection timeout is set as the same number as the timeout given from the > server. Is the Load Balancer causing this type of problem? (specially for > the bytes limit settings?) > > By my surprise, looking at the eclipse error log and svn server log, there > isn't any type of error. > > Regards. > > > On Thu, May 29, 2014 at 2:43 PM, Dmitry Pavlenko <pavle...@tmatesoft.com> > wrote: > >> Hello, >> Usually this error means that the connection is unexpectedly interrupted >> because of unstable network >> connection or because SVN server cuts the connection because of bytes >> sent limit or timeout. Usually >> the problem is successfully solved by operation retrying or SVN server >> configuration to increase >> number of bytes limit and/or timeouts. >> -- >> Dmitry Pavlenko, >> TMate Software, >> http://subgit.com/ - git-svn bridge >> >> >> > I have a huge repository (implemented for years), and I want to perform >> a >> > certain checkout through https protocol. However, almost ending the >> > repository checkout in eclipse, there is an error that throws as >> follows. >> > >> > svn: E175002: chunked stream ended unexpectedly >> > >> > > svn: E175002: REPORT request failed on '/svn/repo/!svn/vcc/default' >> > > svn: E175002: chunked stream ended unexpectedly >> > > svn: E175002: REPORT request failed on '/svn/repo/!svn/vcc/default' >> > > chunked stream ended unexpectedly >> > >> > Sometimes, when I perform the same activity again, there is no error. >> But >> > still, we need to resolve the issue. >> > >> > This is happening under Eclipse's subclipse plugin and using the SVNKit >> > client adapter. >> > >> > >> > The svnkit version that we are using is 1.8.7 (From one of the users). >> But >> > from mine is using the svnkit version 1.8.5 (from subclipse 1.10.4) >> > >> > Regards, >> > >> > Darly Senecal-Baptiste >> > >
