> I sure wish we had a way to reproduce your commit timeout problems.
> You claim http-compression is "no", but IIRC, your win32 client may or
> may not have been reading your registry or config-file. Did you ever
> figure out how to ensure that mod_deflate was totally deactivated on
> the server-side? The fact that you get a timeout *at all* indicates
> to me that the server is still buffering a compressed repsonse.
I deleted the %APPDATA%\Subversion directory and re-ran the svn client to
recreate the directory. Then I set http-compression to "no". I will
double-check before I re-run the client again.
I never did figure out how to ensure deflate was deactivated. My
"BrowserMatch * no-gzip" line did not allow httpd to start. How do you tell
BrowserMatch to match all browsers?
> And what do you mean by "timeout on a large commit corrupted the
> repository"? You mean, you had to run 'svnadmin recover'? That
> shouldn't happen. If the client MERGE repsonse timed out, it means
> the commit succeeded, but the working copy was never notified. But
> there should be any repository recovery problems. (If there are, then
> that's a whole new topic to discuss.)
I'll reproduce the same steps tomorrow when I get to the office. It just
takes a long time to commit over 2GB of mostly binary data.
> As for the checkout -- "chunk read error"? Never even heard of that
> error... from anyone, actually, ever. I'd like to hear more about it.
I'll copy and paste the exact text of the error when I get to the office
tomorrow.
Sly
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 20 16:16:24 2003