Alexander:
It might be possible to baypass load balancer. However, it is not the right
thing. We are actually retrying the checkout and successfully, code gets
checked out.
In my next post (not in svn-kit), I will provide a list of issues that svn
users have when they access the repository server
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. Ther
Hello Darly,
You may resolve the problem either by setting Timeout directive on the
server side to large than default value (in Apache web server
configuration) or by enabling spooling for all operations in SVNKit.
Spooling option, however, is not available for Eclipse plugin - it is only
possible
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 b
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
