write through proxy configuration on windows / apache / svn causing checksum mismatch errors

Hi all,

I am having an interesting issue with a master slave configuration of SVN.

Some files (seems to be larger ones) cause checksum mismatch error as follows:

Checksum mismatch, file '/XXXX XX.png':\n
expected: d37443091695c3f64ebc6f2d4d7a421c\n
actual: 4a28f19a9c8f765f5df26c730bdaeca0\n

during a commit operation. This file does not exist on the server and
it is the initial commit.

My configuration is as follows:

Apache 2.2.11
SVN 1.6.0 (1.5.6 encounters the same error)
OS: Windows XP master and slave (same behavior observed with Windows
2003 server)

I have been able to commit other large file (sizes around 13.5 mega
bytes) without a problem. Also interestingly enough if the file is
committed directly to the master repository this works without a hitch
as well.

When the issue is encountered the error.log on the master machine
shows (no errors are shown on slave):

"mod_dav_svn close_stream: error closing write stream [500, #200014]"

Additional if i calculate MD5 using a code (just writing simple code
for MD5 computing) the result i obtain matches the result calculated
by the svn client ("expected" value).

I have read some articles regarding TCP Large Send options on the
network cards one of the configuration this was tried did have the
setting on the network card which we did try to disable but that did
not resolve the issue either.

I do have a file available which reproduces the issue every time as
well ethereal (now called wireshark) dumps of the transmission.

Just wondering anyone out there has some thoughts on the subject or
things to try out ?

Thank you
-seymen

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1520684

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-02 18:01:59 CEST