Re: imports failing over dav.

My bet is this is a persistent connection handling problem in Apache 2.
The debug traces for import look something like this:

new connection
-> OPTIONS
<- 200
-> MKACTIVITY
<failed to read status line, start new connection>
-> retry the MKACTIVITY
<- 201
-> PROPFIND
<- 207
-> retry the PROPFIND
<failed to read status line, start new connection>

and so on, basically losing the connection every couple of requests.
neon fails gracefully if this happens when it's reading from the socket,
but if it's writing a request body to the socket, we get a SIGPIPE.

I was seeing these with checkouts too. When I turn off persistent
connections in ra_dav, these problems go away, so I'll commit that as a
temporary workaround, and try and work up a simple repro case against
Apache 2.0.

(Thanks to Ben for setting up a test repos so I can play with this!)

joe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:40 2006